Can't find server name when running TRACEROUTE

[Joe Kattner]

Does a dig -x 10.131.149.27 give back the correct and authoritative
response? Check the logs and see if BIND is reporting errors when loading
that zone.
 
-----Original Message-----
From: Vinson Armstead - PA [mailto:Vinson_Armstead at GMACM.COM]
Sent: Wednesday, October 17, 2001 4:12 PM
To: 'Joe Kattner'
Cc: bind-users at isc.org
Subject: RE: Can't find server name when running TRACEROUTE



Joe, 

Thanks for the reply.. 

I have a reverse lookup (PTR) record for the server in my
149.131.10.in-addr.arpa file. I am able to perform reverse lookups on other
entries in that file but not on this node. 

Not really sure why 

-----Original Message----- 
From: Joe Kattner [ mailto:joe.kattner at adelphia.com
<mailto:joe.kattner at adelphia.com> ] 
Sent: Wednesday, October 17, 2001 1:14 PM 
To: Vinson Armstead - PA; bind-users at isc.org 
Subject: RE: Can't find server name when running TRACEROUTE 


You need to configure a reverse entry for 10.131.149.27. 

nslookup causes itself to fail, use dig instead. This is asked very 
frequently, you can check the archives. 

--Joe 






-----Original Message----- 
From: Vinson Armstead - PA [ mailto:Vinson_Armstead at GMACM.COM
<mailto:Vinson_Armstead at GMACM.COM> ] 
Sent: Wednesday, October 17, 2001 11:58 AM 
To: bind-users at isc.org 
Subject: Can't find server name when running TRACEROUTE 


Running BIND 9.1.3 on Solaris for Intel workstations 

When trying to run NSLOOKUP I receive the following error: 

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