BIND resolves all names to only one (wrong) IP from remote clients.

[Kevin Darcy]

Steve Neuharth wrote:

> If I do an nslookup from my new server (freebsd 4.3, bind 8.2.3) of any
> address it works fine....
>
> bash-2.05$ nslookup www.microsoft.com
> Server:  localhost.miniguys.com
> Address:  127.0.0.1
>
> Non-authoritative answer:
> Name:    www.microsoft.akadns.net
> Addresses:  207.46.230.229, 207.46.230.218, 207.46.131.91, 207.46.230.219
>           207.46.131.199
> Aliases:  www.microsoft.com
>
> BUT if I run nslookup from my home (208.42.140.141) and use the new
> server... It resolves every name.. (even names that it should not be
> resolving) to the IP of the nameserver (208.42.18.3)...
>
> C:\>nslookup
> > server 208.42.18.3
> Default Server:  cthompson.dsl.visi.com
> Address:  208.42.18.3
> > nslookup www.microsoft.com
> Server:  www.microsoft.akadns.net
> Addresses:  208.42.18.3, 208.42.18.3, 208.42.18.3, 208.42.18.3
>           208.42.18.3
> Aliases:  www.microsoft.com
>
> *** www.microsoft.com can't find nslookup: Non-existent domain
>
> WHAT'S THE DEAL?

  Looks like it might be a combination of incorrect command syntax and a
horrible bug in your version of nslookup. Note that you typed "nslookup
www.microsoft.com" at the nslookup command prompt instead of just
"www.microsoft.com". Looks like nslookup misinterpreted your command, looked
up www.microsoft.com, got the answer, replaced all of the addresses in the
response with your server's address, and then complained that the name
didn't exist.

Yet another reason to not use nslookup.

Does it work if you use correct command syntax?


- Kevin