sysquery: nlookup error on ?

[Joseph S D Yao]

On Fri, Jul 14, 2000 at 11:25:41AM -0400, unknown wrote:
> my dns (bind8) was working fine.. then i don't know probably i did something
> and
> now when i do ndc restart or ndc stop and ndc start it says its starting and
> i can't use nslookup and in /var/log/messages i'm geting this
> 
> Jul 14 11:20:23 ns1 named[15659]: starting.  named 8.2.2-P5 Sat Nov 27
> 13:52:39 CST 1999 ^Iroot at blackhole:/tmp/bind-8.2.2-P5/src/bin/named
> Jul 14 11:20:23 ns1 named[15659]: listening on [127.0.0.1].53 (lo)
> Jul 14 11:20:23 ns1 named[15659]: listening on [63.251.19.66].53 (eth0)
> Jul 14 11:20:23 ns1 named[15659]: listening on [192.168.0.66].53 (eth0:1)
> Jul 14 11:20:23 ns1 named[15659]: Forwarding source address is
> [0.0.0.0].1053
> Jul 14 11:20:23 ns1 named[15660]: Ready to answer queries.
> Jul 14 11:20:23 ns1 named[15660]: sysquery: nlookup error on ?
> 
> Jul 14 11:13:53 ns1 named[15650]: sysquery: nlookup error on ?
> Jul 14 11:15:42 ns1 named[15650]: No root nameservers for class IN
> Jul 14 11:15:42 ns1 named[15650]: sysquery: nlookup error on ?

Make sure that you have a "hint" zone for "." in "/etc/named.conf".
Make sure that the file to which it refers has the root name servers
listed in it, both as NS records for ".", and with "A" records for each
one.  Make sure that this file is readable to 'named'.

Once this is done, see if you have any other problems.

Use RCS, CVS, SCCS, or any commercial file management package to keep
track of version control on any text file that you consider at all
important.  That way you won't have this "how did I get here from
there, and where was there?" problem.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.