sysquery: nslookup error

Barry Margolin barmar at genuity.net
Thu May 25 19:52:59 UTC 2000


In article <20000525163301.C25244 at orange.keble.ox.ac.uk>,
Simon Huggins  <huggie at earth.li> wrote:
>Hi,
>
>I've just browsed the archives of this list and I can see other people
>with similar problems but haven't seen any useful answers yet...
>
>Essentially I am running DNS for a tiny network but also dialup and want
>bind to do DNS for the LAN at all times and DNS for the outside world
>when I'm dialled up.
>
>With 8.1.2 this was easy (no I wasn't listening on the ppp device) but I
>thought in spite of trusting my housemates I should probably upgrade and
>did the other day.
>
>I now get lots of logs of "sysquery: nslookup error" when in the offline
>configuration (essentially with the zone "." commented out).
>When I am online and uncomment it and have access to the root servers
>everything is fine.

Instead of commenting out the zone ".", make your server a master for that
zone when you're offline; create a trivial master zone file that just
contains an SOA and NS record.  When you're online, put back the hints
zone and restart named.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list