reverse lookup with "server failed" error message

Michael Coburn Michael.Coburn at mailbits.com
Tue Oct 24 18:45:39 UTC 2000


Problem FIXED.  Turns out I had my reverse zone file statement wrong.  It
was   zone "0.250.117.250.in-addr.arpa" etc....

it should have been

zone "250.117.250.in-addr.arpa" etc...

Nominum is a great resource.

Thanks to all for your responses.

-----Original Message-----
From: kcd at daimlerchrysler.com [mailto:kcd at daimlerchrysler.com]
Sent: Thursday, October 19, 2000 6:02 PM
To: bind-users at isc.org
Subject: Re: reverse lookup with "server failed" error message



Michael Coburn wrote:

> Ok heres my problem.  Every time I restart bind "ndc restart"  I can do a
> reverse lookup 2 times and then I get server Failed.

Those are three *different* invocations of nslookup, thus confusing
diagnosis.

Is it always the *same* reverse lookup that fails? If so, focus on what is
different about that particular reverse record.

> Any ideas?  I've seen this error message on the list but I haven't seen a
> resolution.  All I have heard is that it is a problem with nslookup.

As much as I'd like to blame this on on nslookup, SERVFAIL is a fairly
generic *server* response. You should be looking on the server side to see
why the reverse lookup is failing.


- Kevin

>
>
> [root at ns1 mcoburn]# nslookup 209.117.250.131
> Server:  ns1.int.mailbits.com
> Address:  10.4.0.8
>
> Name:    mailbits.net
> Address:  209.117.250.131
>
> [root at ns1 mcoburn]# nslookup 209.117.250.133
> Server:  ns1.int.mailbits.com
> Address:  10.4.0.8
>
> Name:    go.mailbits.com
> Address:  209.117.250.133
>
> [root at ns1 mcoburn]# nslookup 209.117.250.100
> Server:  ns1.int.mailbits.com
> Address:  10.4.0.8
>
> *** ns1.int.mailbits.com can't find 209.117.250.100: Server failed
> [root at ns1 mcoburn]#









More information about the bind-users mailing list