Internal DNS?

[Kevin Darcy]

The address in the error message (10.81.11.18) doesn't match the address in
the command line (10.1.1.254). Is this for real, or did you just make a
mistake when trying to "anonymize" the addresses for purposes of this post?

In any case, the basic problem here is that nslookup sucks. Among other
flaws, it aborts when it can't reverse-resolve the address of the nameserver
it is trying to use. Real lookup tools like "dig" don't have this problem. Of
course, you can probably get around the immediate problem by setting up a
reverse record for 10.1.1.254 (or 10.81.11.18 or whatever the real address
is). But nslookup's flaws are likely to bite you in other ways, so you should
seriously consider ditching it and using something else instead.

At the very least, try using the -debug command-line option to nslookup so
you can see what on earth it's doing.


- Kevin

Chris Murley wrote:

> I have an internal DNS server, on 10.1.1.254
>
> I have an internal workstation, at 10.1.1.2
>
> They are box redhat linux, when I do an:
>
> > nslookup 10.1.1.2 10.1.1.254
>
> i get:
>
> *** Can't find server name for address 10.81.11.18: Non-existent
> host/domain
> *** Default servers are not available
>
> my /etc/resolv.conf on the workstatison looks like:
>
> search inn.lee.net
> nameserver 10.1.1.254
>
> Bubt from the console of 10.1.1.254 i can look up things fine, just not on
> another machine.
>
> ANy ideas?
>
> -Chris
>
> -----------------------
> Christopher Murley
> Application Index
> http://www.appindex.net
> http://www.appindex.org
> -----------------------
>
> k