unknown hosts appear to resolve

Barry Margolin barmar at bbnplanet.com
Wed Jul 7 23:26:58 UTC 1999


In article <3783B344.1009AFF6 at ericsson.com>,
Mark Steph  <mark.steph at ericsson.com> wrote:
>
>I am positive I have something stupid and obvious wrong, but I can't seem
>to find the answer anywhere else, so here goes.  (Probably searching with
>the wrong keywords...)
>
>I have 2 DNS servers for 2 separate domains.  They are (supposedly) built
>exactly alike.  (Obviously, this is not *really* the case).  Sunos 5.6,
>same hardware, same patches, bind 8.2.1.
>
>server1:
>> nslookup noexist.com
>Server:  server1.domain1.com
>Address:  1.2.3.4
>
>Name:    noexist.com.domain1.com
>
>(It should return some NXDOMAIN error here...)

Do you have a wildcard record in domain1.com?  When nslookup finds that
noexist.com doesn't exist, it retries the lookup with the domains in your
search list appended, so it looks for nexist.com.domain1.com.  This matches
the *.domain1.com entry, so it returns that.

Presumably domain2.com doesn't have a wildcard record, which is why things
work differently there.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, 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