Resolver Error 0 (no error)

Pete Ehlke pde at ehlke.net
Thu Oct 9 18:29:32 UTC 2003


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


More information about the bind-users mailing list