dns server doesn't know itself (NT BIND v 4.9.5)
Michael Voight
mvoight at cisco.com
Mon Aug 9 18:06:10 UTC 1999
It is much simpler than that.
The 1.1.10.in-addr.arpa zone is misconfigured.
Michael
Jim Reid wrote:
>
> >>>>> "Steve" == Steve Hammill <shammill at earthlink.net> writes:
>
> Steve> Here's the NSLOOKUP error message:
> Steve> *** can't find server name for 10.1.1.254: non-existent domain
> Steve> *** can't find server name for 10.1.1.254: non-existent domain
> Steve> server: unknown
> Steve> address:10.1.1.254
>
> Steve> ping by name works...
> Steve> nslookup works once I issue the server command...
>
> Looks like you have a version of nslookup that likes to make obsolete
> inverse queries - not the same thing as a reverse lookup! - and your
> name server doesn't support these. Try getting a better version of
> nslookup. Better still, throw nslookup in the bin and use host or dig
> for sending DNS queries and general troubleshooting.
More information about the bind-users
mailing list