Solaris 9 , nslookup fails , dig works 1

[elemica]

Hi all

nslookup returns unable to reach nameserver, dig resolves . See output below.

# nslookup

http://www.google.com

*** Can't find server name for address 192.168.176.20: Non-existent host/domain
*** Can't find server name for address 192.168.176.15: Non-existent host/domain
*** Default servers are not available

# dig

http://www.google.com

; <<>> DiG 8.3 <<>>

http://www.google.com

;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;

http://www.google.com,

type = A, class = IN

;; ANSWER SECTION:

http://www.google.com.

15M IN CNAME

http://www.l.google.com.

http://www.l.google.com.

5M IN A 66.102.7.104

http://www.l.google.com.

5M IN A 66.102.7.99

http://www.l.google.com.

5M IN A 66.102.7.147

;; Total query time: 129 msec
;; FROM: osiadmin to SERVER: default -- 192.168.176.20
;; WHEN: Mon Nov 14 11:51:04 2005
;; MSG SIZE sent: 32 rcvd: 100

I am able to ping and telnet the name server on port 53.

Would appreciate inputs on what could be wrong.

TIA

 

[coffeysm]

Hmm obviously your /etc/resolv.conf is setup if dig is working correctly. Have you tried running a truss nslookup to see what causes the error?

 

[elemica]

Thanks for the response.

Strange but I changed the name server to another one and nslookup & dig works just fine. Not able to explain why this should be.

Appreciate the resonse.

 

[elgrandeperro]

I believe that nslookup asks your configured DNS server to reverse its own IP address. If that fails, I believe that is the failure you are seeing, that 192.168.176.15 and 192.168.176.20 aren't configured for reverse dns of their ips.

gene

 

[elemica]

Gene

Thanks for the response. What you mentioned could be the likely cause.