Unix client resolving differently

[Cinense, Mark]

Simon,

>First nslookup really sucks for DNS troubleshooting - learn dig.

	No problem using dig here...

Windows DIG results:

F:\>dig @ns3.sandia.gov ANY chivas.mp

; <<>> DiG 9.2.1 <<>> @ns3.sandia.gov ANY chivas.mp
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;chivas.mp.                     IN      ANY

;; ANSWER SECTION:
chivas.mp.              43200   IN      A       64.65.105.59

;; AUTHORITY SECTION:
mp.                     43200   IN      NS      ns1.nic.mp.
mp.                     43200   IN      NS      ns2.nic.mp.

;; Query time: 460 msec
;; SERVER: 134.253.181.25#53(ns3.sandia.gov)
;; WHEN: Tue Nov 19 05:59:35 2002
;; MSG SIZE  rcvd: 83


UNIX DIG results:

# dig @ns3.sandia.gov ANY chivas.mp

; <<>> DiG 9.2.1 <<>> @ns3.sandia.gov ANY chivas.mp
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 415
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;chivas.mp.                     IN      ANY

;; ANSWER SECTION:
chivas.mp.              43082   IN      A       64.65.105.59

;; AUTHORITY SECTION:
mp.                     43082   IN      NS      ns1.nic.mp.
mp.                     43082   IN      NS      ns2.nic.mp.

;; Query time: 12 msec
;; SERVER: 134.253.181.25#53(ns3.sandia.gov)
;; WHEN: Tue Nov 19 06:02:03 2002
;; MSG SIZE  rcvd: 83

BTW, my resolv.conf does have a search entry for my domain.  I looked
further into this issue, and noticed that I was using a different nslookup
from what came with bind 9, which is what I am running here at sandia.  I
tried that one, and still no luck.  I have to use the fully qualified name,
and then it resolves correctly.  Our legato server is resolving by short
name, and not FQDN.  I don't know how they are doing that, but they are.


Mark