Resolver Error 0 (no error)

[Bobby Johnson]

I wish that were my problem, but I get the same error with other servers as
well...
> nslookup www.dell.com ns-east.cerf.net
*** Can't find server address for 'ns-east.cerf.net': Resolver Error 0 (no
error)

Server:  ns.mydomain.com
Address:  10.10.10.12

Non-authoritative answer:
Name:    www.ins.dell.com
Address:  143.166.224.230
Aliases:  www.dell.com


I just noticed the error that dig displays....
> dig @ns-east.cerf.net www.dell.com

; <<>> DiG 8.3 <<>> @ns-east.cerf.net www.dell.com
; Bad server: ns-east.cerf.net -- using default server and timer opts
; (1 server found)
[snip]

The answer gets provided by my server instead of the ns-east.cerf.net
nameserver.

I can successfully resolve ns-east.cerf.net (nslookup and/or dig)...

> nslookup ns-east.cerf.net
Server:  ns.mydomain.com
Address:  10.10.10.12

Non-authoritative answer:
Name:    ns-east.cerf.net
Address:  207.252.96.3


Thanks for your time,
--
Bobby Johnson 
e-Security, Inc. 
Enterprise Security Management 
bobby.johnson at esecurityinc.com 
www.esecurityinc.com 
 


-----Original Message-----
From: Pete Ehlke [mailto:pde at ehlke.net] 
Sent: Thursday, October 09, 2003 2:30 PM
To: Bob
Cc: comp-protocols-dns-bind at isc.org
Subject: Re: Resolver Error 0 (no error)


On Thu, Oct 09, 2003 at 09:52:56AM -0700, Bob wrote:
> I'm installing a new Solaris DNS server running Bind 9.2.2.  This 
> system is in a DMZ and the firewall is NAT translating to a public IP 
> address.
> 
> At first glance it appears to properly resolve the zones that it is 
> authoritative for and it is retreiving the proper addresses for 
> external systems.
> 
> But there is one test that is giving me an odd result and I'm just not 
> sure what's going on.  When I specify another nameserver on the 
> command line for nslookup, I get a no-error error, and then get a
> (correct) response from the *local* nameserver instead of the 
> specified one.
> 
> > nslookup www.cisco.com ns1.cisco.com
> *** Can't find server address for 'ns1.cisco.com': Resolver Error 0 
> (no error)
> 
This is a coincidence of the server that you chose :)

Cisco had a DNS configuration problem over the past couple of days that
manifested itself as some of their servers reporting that ns1.cisco.com had
an address in RFC 1918 space. Cascading errors in rsolvinf cisco.com
namespace were... interesting.

-Pete