nslookup fails on first try, help!

[Kevin Darcy]

Presumably named is still initializing when you issue the first query; are
you querying it before the "Ready to answer queries" message is written to
the log?

As for why it would take a long time to initialize, I can only guess. Lots
of zones? Perhaps the "priming" query to the root servers is taking a long
time for some reason? Maybe it can't talk to the root servers AT ALL??? You
probably have to look more closely at the logs, or possibly even turn on
debugging, to find out what the slowdown is.


- Kevin
Rev. Ferret wrote:

> I recently set up a DNS server on my machine.  It appears to be working
> exceprt for one thing.   If I boot the machine, and log in shortly after
> it is done booting, and type 'nslookup', I get the following message:
>
> ***Can't find server name for address 127.0.0.1: No response from server
>
> It then goes to my secondary nameserver.
>
> Then, if I exit nslookup, and do it again, it says my nameserver is
> 127.0.0.1, just like it is supposed to.  Or, if I boot the machine, then
> restart named before doing any nslookup's, it will work the first time I
> try it.
>
> Anybody know what could be causing this problem, and what file I should
> look in?  I've been trying to figure this out for a day now and it's
> driving me nuts.
>
> Thanks,
> Steve