sysquery: nlookup error on ?

[Kevin Darcy]

There are 2  errors here:

"sysquery: findns error (NXDOMAIN) on ns2.zanmai.net.coprop.com?"
This one is in the messages reference at http://www.acmebw.com/askmrdns/b=
ind-messages.htm and
means that the nameserver encountered an NS which has no matching A recor=
d. Looks like
someone forgot the trailing period in the "coprop.com" zone file...

"sysquery: nlookup error on ?"
Hmmm... Somehow this error appears to be missing from the messages refere=
nce. But experience
tells me that it indicates a problem with "priming". When "named" starts =
up, it expects to
get root-zone data, either by directly querying the servers listed in the=
 "hints" file, or,
if global forwarding is configured, by doing a root-zone query through th=
e forwarder. If this
"priming" operation is unsuccessful, it has no root zone information, and=
 this could cause
the "sysquery: nlookup error on ?" messages, although I wouldn't expect t=
o see this error if
global forwarding is enabled, since in that case it shouldn't need any ro=
ot-zone data for
referral purposes. You're not trying to use an Internet hints file behind=
 a firewall that
blocks DNS queries, are you? In that case, you need to set up forwarding =
if you want to be
able to resolve Internet names.


- Kevin

Jerri Blavitt=B3 wrote:

> We have a (new/unfamiliar) OS (RedHat) on a new machine AND just upgrad=
ed to the new spec
> of BIND.
>
> machine: zanmai.net www ww2 ww3 ns
> nameservers: ns.zanmai.net ns1.zanmai.net ns2.zanmai.net
>
> Or error logs are filing with the stuff below and occasionally our IFCO=
NFIG
> file seems to spontaneously unbind its list of ethernet IPs ...
>
> I spent hours trying to locate the error to no avail, any help would be=
 greatly
> appreciated.
>
> Thanks in advance,
> Jerry
>
> This from the logs on zanmai.net (which is also the same machine as ns.=
zanmai.net. ns1 and
> ns2 are separate boxes)
>
> Sep  1 11:47:41 ww3 named[6901]: sysquery: findns error (NXDOMAIN) on
> ns2.zanmai.net.coprop.com?
>
> Sep  1 12:06:11 ww3 named[6901]: NSTATS 967809971 967727178 0=3D3 A=3D1=
6533 CNAME=3D179 SOA=3D876
> PTR=3D3 MX=3D5
> 96 AAAA=3D7 ANY=3D22
>
> Sep  1 12:06:11 ww3 named[6901]: XSTATS 967809971 967727178 RR=3D345 RN=
XD=3D0 RFwdR=3D0 RDupR=3D0
> RFail=3D0 RF
> Err=3D0 RErr=3D345 RAXFR=3D0 RLame=3D0 ROpts=3D0 SSysQ=3D345 SAns=3D177=
85 SFwdQ=3D0 SDupQ=3D6 SErr=3D0
> RQ=3D18221 RIQ=3D0 RF
> wdQ=3D0 RDupQ=3D0 RTCP=3D437 SFwdR=3D0 SFail=3D0 SFErr=3D0 SNaAns=3D146=
96 SNXD=3D87
>
> Sep  1 12:06:25 ww3 named[6901]: sysquery: nlookup error on ?
>
> Sep  1 12:34:30 ww3 named[6901]: sysquery: nlookup error on ?
> Sep  1 12:35:39 ww3 last message repeated 7 times
> Sep  1 12:36:44 ww3 named[6901]: sysquery: nlookup error on ?
> Sep  1 12:38:22 ww3 last message repeated 4 times
> Sep  1 12:39:32 ww3 last message repeated 9 times
> Sep  1 12:41:00 ww3 last message repeated 2 times