server failed

Joseph S D Yao jsdy at cospo.osis.gov
Fri Jun 4 17:51:08 UTC 1999


> Michael Voight <mvoight at cisco.com> wrote in message
> 375589D4.1F6C29A1 at cisco.com...
> >Server failed generally happens if the query is directed to a server
> >that is supposed to be authoritative for the domain, but isn't.
> 
> Just to clarify...  it will happen when a server tries *all* supposedly
> authoritative servers and comes up empty handed.
> 
> >So, it is possible the outside machine's nameserver show multiple NS
> >records for your domain and all of the servers listed in the NS records
> >are not servers for the domain in question.
> 
> If yes, then the delegation information with your parent domain (com maybe?)
> likely needs to be updated.

To put this to rest, this is exactly what happened.  Although inQuo had
shared authority and slaved to their forward domains, they had not done
same to their reverse domains.  The requester has been told that he
needs to get them to do this for future happiness and harmony.  ;-)

--
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.



More information about the bind-users mailing list