Unix client resolving differently

[Danny Mayer]

At 04:32 PM 11/18/02, Cinense, Mark wrote:

>I was wondering if anyone has seen this.  I have 2 BIND servers internally
>behind a firewall, and they do not communicate with any of the root servers,
>or any nameserver except for my 2 external BIND servers.
>
>For some strange reason, when you are on a Unix machine, you do a lookup on
>chivas.mp, the nameserver will return 64.65.105.59.  However on an MS box,
>you do the same lookup and it returns what my zone file has in it.  So for
>example:
>
>UNIX machine:
>
># nslookup chivas.mp
>Server:  ns4.sandia.gov
>Address:  134.253.45.135
>
>Non-authoritative answer:
>Name:    chivas.mp
>Address:  64.65.105.59
>
>WINDOWS machine:
>
>F:\>nslookup chivas.mp
>Server:  ns4.sandia.gov
>Address:  134.253.16.5
>
>Name:    saux016.sandia.gov
>Address:  134.253.246.128
>Aliases:  chivas.mp.sandia.gov

The address for the server that the windows machine is using is different
from the address for the server that the Unix machine is using, even
though they have the same name. So there are different servers
giving different responses. You need to look at the resolv.conf file in the
case of the Unix machine and the Windows Network gooey in the case
of Windows. The search list is important as is the domain name. If you
are using Microsoft's version of nslookup, I don't know how it handles
search lists, I just know you can put them in. In the Windows case it
may have appended the IP domain name.

Use dig for these kinds of queries. It's available for Windows.

Danny
>I had the client do a snoop on the packets, and looks like the Unix machine
>is sending out the query like this:
>
>Chivas.mp.
>
>Which is really strange.
>
>I am not sure why it is doing this.  Can someone please help.
>
>Mark