nslookup not working correctly with dns servers

A

artcurmudgeon

In a nutshell, I have a couple of people in my dept that want to use nslookup and I am in the process of rebuilding the dns servers and upgrade them.

When someone trys an nslookup this is what they get...

Code: 
*** Can't find server name for address 10.97.4.21: Server failed
*** Can't find server name for address 10.97.4.22: Server failed
*** Default servers are not available
Server:  UnKnown
Address:  10.97.4.21

Name:    google.com
Addresses:  209.85.225.147, 209.85.225.99, 209.85.225.103, 209.85.225.104
	  209.85.225.105, 209.85.225.106

I am at a bit of a loss...

Any thoughts?

Thanks
 
This looks like a typical MS error. I think MS products complain when nameservers do not have correct PTR records, and even invalidate nameservers that don't resolve. From the looks of it, this is not a fatal error, because resolving does appear to take place. If you can manage to make the IP addresses 10.97.4.21 and 10.97.4.22 resolve to a hostname (and the other way around) these warnings will probably disappear.
 
it turns out that the reverse for .21 and .22 were both wrong.

I inherited this setup from the previous sysadmin who was promoted, the old dns server has a setup listed in it from about a year ago when they converted ip schemes and when to a ms dhcp server(before anyone kills me this is school and there are some ms products they need).

I found a reference in the reverse list that pointed to the old numbering scheme, once corrected and brought up to date, it works correctly.

thanks again to all
 
From Bernsteins mumblings about nslookup in http://cr.yp.to/djbdns/nslookup.html
What exactly is nslookup doing wrong? Three things:

  • Before doing what you tell it to do, nslookup tries a PTR query on the server's IP address, so that it can tell you the server's name, as if this information were more useful than the name or IP address that you gave nslookup in the first place.

  • When you specify a server on the command line, nslookup sends its silly PTR query to that server, unjustifiably assuming that the server is recursive or already has the answer. Correct behavior would be to ask the local cache.

  • If the silly PTR query fails, nslookup aborts, and never does what you told it to do.
Click to expand...
 
True. Which is why nslookup is deprecated and tools like host and dig are preferred. Not sure which options MS has.
 
You must log in or register to reply here.
Back
Top