Almost all non-existent domains resolve to localhost

Barry Margolin barmar at genuity.net
Tue Aug 21 17:26:54 UTC 2001


In article <9lu587$jgs at pub3.rc.vix.com>,
≈ chris ≈ <whirlwind at graffiti.net> wrote:
>
>Hi group,
>
>
>Something funny going on and I could use some assistance:
>
>[root at mybox /etc]# nslookup aaaaaaaaargh.com
>Server:  mydns.com
>Address:  12.34.56.78
>
>*** mydns.com can't find aaaaaaaaargh.com: Non-existent host/domain
>
>[root at mybox /etc]# nslookup aaaaaaaaargh.net
>Server:  mydns.com
>Address:  12.34.56.78
>
>Name:    aaaaaaaaargh.net.mydns.com
>Address:  12.34.56.78
>
>
>As you can see, all non-existent domains (except for those ending in
>.com), are resolving to localhost... (fake addresses used in example
>above)
>
>What could be causing this?

A wildcard A record in your domain:

*.mydns.com. IN A 12.34.56.78

As for why it doesn't happen to names ending in .com, my guess is that you
have an entry for com.mydns.com, which is shadowing the wildcard in that
case.  This seems unlikely to me, so there's probably another explanation
that I can't think of offhand.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list