There's no reverse dns entry for the IP. nslookup tries to resolve the IP of the server to the name and it fails. It is still able to resolve the forward lookup and gives you that answer.
Dan On Tue, 2002-06-11 at 13:38, IMail Admin at BC Web wrote: > Hi, > > This is a bit off-topic, but this has always been my favorite place to get > answers to tricky questions like this. > > We had an arrangement with our backend ISP where they provide us with > secondary DNS service. We switched backend ISPs, and so we made new > arrangements for a secondary DNS. The problem is that in testing this new > arrangement, we're getting a strange error message. > > Our own address pool is 66.224.41.x, and our new secondary DNS server is > 204.250.116.119. I believe they set this up as a secondary IP on that > server (it also holds either .17 or .18 as its primary IP) so that they > would have the option of later splitting the IPs (running one DNS server on > .18 and one on .19). We created an A record in our zone that points to this > new secondary DNS server. So the A record is for dns2.bcwebhost.net > pointing to 204.250.116.119. > > Now for the error message: > When I run nslookup against the new secondary DNS server, I get the right IP > back, but I also get an error message. Here is an example: > > [within a command prompt on a Win2k machine] > ************************************************************** > C:\WINNT\system32>nslookup www.bcwebhost.net 204.250.116.19 > *** Can't find server name for address 204.250.116.19: Non-existent domain > Server: UnKnown > Address: 204.250.116.19 > > Name: www.bcwebhost.net > Address: 66.224.41.51 > > > C:\WINNT\system32> > ************************************************************** > > That was referencing the secondary DNS server by IP. When I reference it by > name, I get this result: > ************************************************************** > C:\WINNT\system32>nslookup www.bcwebhost.net dns2.bcwebhost.net > *** Can't find server address for 'dns2.bcwebhost.net': > Server: bcnetserv.bednarzconsulting.com > Address: 10.0.0.1 > > Name: www.bcwebhost.net > Address: 66.224.41.51 > > > C:\WINNT\system32> > ************************************************************** > > This was performed inside our network, so it apparently got the right IP by > going to our primary DNS internal server (which forwarded the request to the > real primary DNS server). > > My questions: > > 1. In the first scenario, what does it mean by "Can't find server name for > address 204.250.116.19: Non-existent domain"? > 2. In the second scenario, why did we get "Can't find server address for > 'dns2.bcwebhost.net'"? > > Thanks, > > Ben > BC Web > > > Please visit http://www.ipswitch.com/support/mailing-lists.html > to be removed from this list. > > An Archive of this list is available at: > http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ > > Please visit the Knowledge Base for answers to frequently asked > questions: http://www.ipswitch.com/support/IMail/ -- Dan Shadix Computer Network Manager Terry Reilly Health Services 208-467-4431 Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
