On Mon, 25 Mar 2002, Anand Kumria wrote:
> On Mon, Mar 25, 2002 at 10:40:49AM +1100, Ben Donohue wrote:
>
> Not really; nslookup is _using_ 172.31.8.12 to perform its lookups (recursively).
>
> > however then I do a
> > nslookup www.mazda.com 172.31.8.12 (this is the new secondary DNS)
> > it replies...
> > *** Can't find server name for address 172.31.8.12: Non-existent host/domain
> > *** Default servers are not available
> >
> > Why isn't it looking to its own cache for this resolution?
>
> Quite possibly it isn't authoritative. I tend to find the `dig' command simpler to
>use;
> try
>
> $ dig www.mazda.com
>
> then
>
> $ dig www.mazda.com @172.31.8.12
>
> The @<ip> causes to dig to only query that particular server. You'll want to look
> for the response header section and see that there is no 'NXDOMAIN' or `NOHOST'. It
> should be 'NOERROR' if all is well and return the data you expect.
>
> Anand
>
>
More likely, your problem is just that nslookup is braindead.
You've asked it to get a record (presumanly an A record) on the name
www.mazda.com from the server on 172.31.8.12
nslookup decides that before it does that, it will be a bit clever, and
tell you what name is associated with 172.31.8.12.
What's probably happening here is that there *isn't* a name associated
with 172.31.8.12. Rather than getting on with life despite it's plans not
quite working perfectly, nslookup instead decides to have a sook, and not
bother actually doing what you originally asked it to.
That "*** Can't find server name for address 172.31.8.12: Non-existent
host/domain" messages is nslookups way of saying "I tried to be a bit
clever, but it didn't work, so now i'm on strike"
The solution is simple: use dig. Dig does what you ask it to. It doesn't
try going off on it's own bat and trying to do things that it thinks might
make life more interesting.
</rant>
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
