Servfail When Resolving certain domains

England, Robert (Robert) england at northamerica.exchange.agere.com
Mon Dec 10 22:00:00 UTC 2001


Isn't there a way around this? If I do a 

zone "zaiqtech.com" in {
      type forward;
      forwarders { 206.34.200.2; 206.34.200.3; };
};

in our named.conf the mail gets sent and everybody is happy. But I don't
want to have to do this for every domain that I find an error for. I have
tried sending the domain admin in the SOA an email, but I don't have the
time to track down every admin to tell them they have DNS issues. 

Why does the zone forward work? I saw the NS record issues but I still need
to understand why the zone forward works and not the straight DNS query that
follows the top down approach (db.cache) that for 99% of the domains we
email daily.

-Bob

-----Original Message-----
From: Jim Reid [mailto:jim at rfc1035.com] 
Sent: Monday, December 10, 2001 4:37 PM
To: England, Robert (Robert)
Cc: 'Bind-Users-Group'
Subject: Re: Servfail When Resolving certain domains 

>>>>> "Robert" == England, Robert (Robert)
<england at northamerica.exchange.agere.com> writes:

    Robert> I'm trying to figure out why our DNS servers are having
    Robert> intermittent problems getting to a hand full of domains on
    Robert> a consistent basis. Below is one of the domain names we
    Robert> continually have issues with. We run a BIND 8.2.4
    Robert> environment.
 
    Robert> $ /usr/sbin/dig zaiqtech.com mx

The delegation for zaiqtech.com is messed up. The servers for .com say
it is served by ns2.connactivity.com and connactivity.connactivity.com.
However neither of these servers is authoritative for this zone. Both
of them claim the zone is served by a different set of name servers,
only one of which -- connactivity.connactivity.com -- is listed in the
parent zone. And that server isn't authoritative for it. Complain to
the administrators of both zones. How you do this is left as an
exercise to the reader. :-)


More information about the bind-users mailing list