Weird nslookup result on a non-existant domain.
Kevin Darcy
kcd at daimlerchrysler.com
Sat Feb 24 01:35:06 UTC 2001
Looks like you have a wildcard CNAME entry in mydomain.dk. Either get rid
of that or get rid of the default domain or searchlist from
/etc/resolv.conf, or just dot-terminate all external names when using
nslookup (note that "dig" doesn't suffer from this bogosity).
- Kevin
P.S. Re: your .sig. By the way, UNIX will be a full billion years old, as
measured by ctime, later this year. But BonaFideGeeks(tm) will probably
prefer to celebrate at 2^30 seconds (C1G or "ctime 1 gig"), which doesn't
happen until 2004.
David P. Hansen wrote:
> Hi,
>
> after I upgraded bind to 8.2.3, I've been getting this weird output from
> nslookup, when I try to resolve a bongus domainname:
>
> mydomain:~% nslookup blah.dumidej.dk
> Server: localhost
> Address: 127.0.0.1
>
> Non-authoritative answer:
> Name: mydomain.dk
> Address: v.x.y.z
> Aliases: blah.dumidej.dk.mydomain.dk
>
> Where mydomain.dk is the domainname for the Linux box.
>
> What it should do, is to say that blah.dumdidej.dk doesn't exist.
>
> I've tried the FAQs, the documentations, and the archive... but haven't
> been able to find a solution for the problem :\ - hope you guys can help
> :)
>
> /david
>
> --
> UNIX was half a billion (500000000) seconds old on
> Tue Nov 5 00:53:20 1985 GMT (measuring since the time(2) epoch).
> -- Andy Tannenbaum
More information about the bind-users
mailing list