Strange NSLOOKUP behavior

Barry Margolin barmar at genuity.net
Fri Aug 24 17:29:40 UTC 2001


In article <9m615n$d2k at pub3.rc.vix.com>,
morgan lynder  <klaus_knomi at yahoo.com> wrote:
>
>Hello,
>I have Bind 9.1.3 installed on Solaris 8. My server is
>able to answer queries that originate from the outside
>world. However the ohter machines on the network fail
>trying to querie the nameserver. The error is:
>
>atfish# /usr/sbin/nslookup
>*** Can't find server name for address 216.203.228.98:
>Server failed
>*** Default servers are not available
>
>
>Now this error message is returned immediately.
>Usually when this error message appears the nslookup
>command will time out before returning this,
>indicating a broken nslookup binary. Since this
>message is returned instantly I don't think this is
>the case. All the machines do indeed have a route to

"Server failed" means that the nameserver responded with a SERVFAIL error
code when queried.  Your nameserver is unable to translate its own address
to a hostname, although the reverse domain is delegated to it.

You need to fix the reverse DNS on your nameserver.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list