Bind 9.1 resolver issue

[Kevin Darcy]

Why do you *need* nslookup to work remotely? nslookup sucks. One of its more
annoying traits is that it aborts if it can't reverse-resolve the address of
the nameserver(s) it is trying to use. dig and host omit this "feature".
Chances are you haven't set up reverse resolution for the
(non-loopback) address of the nameserver. That's why nslookup fails remotely.


- Kevin

Matthew A.R. Sherian wrote:

> I have a nameserver up and working locally. It is an open query server.
> However I am unable to get remote machines using nslookup to resolve against
> the server. Locally nslookup works. Dig and host work remotely. Is there
> anything that I have to do in order to have backwards compatability?