checkhints: unable to get root NS rrset from cache: not found

[Todd Snyder]

Peter,

Ours was something to do with the subnets that were allowed to do
specific queries.  I didn't work on the issue, just heard about it in a
meeting.  I do remember that error message though, and it's one we look
out for now as an indicator that a subnet may not be able to query that
server. 

I wish I could be more help, but hopefully the little details might
tweak something in your mind while you troubleshoot.

Cheers,

Todd.

-----Original Message-----
From: Peter Davies [mailto:pdavies6 at csc.com] 
Sent: Wednesday, August 20, 2008 9:30 AM
To: Todd Snyder
Cc: bind-users at isc.org
Subject: RE: checkhints: unable to get root NS rrset from cache: not
found

Hi Todd,
        I done use acl lists much just a couple of the to allow zone
tranfsers on a few domiains Here's the option block  from the config
file options {
        directory "/var/named";
          allow-transfer { none; };
          allow-query { any; };
          allow-update { none; };
          recursive-clients 1500;
          pid-file "/var/run/named.pid"; };

Peter Davies
CSC Airline Solutions
Engvej 155
DK-2300 Copenhagen S, Denmark
Tel. +45 3614 5737
pdavies6 at csc.com
www.csc.com/dk

CSC Airline Solutions Denmark A/S
Registered Office: Engvej 165, 2300 Copenhagen S, Denmark Registered in
Denmark No: 14278176

------------------------------------------------------------------------
------------------------------------------------------------------------
-------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of
e-mail for such purpose.
------------------------------------------------------------------------
------------------------------------------------------------------------
-------------------------




"Todd Snyder" <tsnyder at rim.com>
20-08-2008 14:59

To
Peter Davies/SCA/CSC at CSC
cc

Subject
RE: checkhints: unable to get root NS rrset from cache: not found






After an upgrade, we started seeing that happen when ACL's weren't setup
to allow recursion, I believe.  Maybe you have a similar issue?

t. 

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Peter Davies
Sent: Wednesday, August 20, 2008 8:30 AM
To: bind-users at isc.org
Subject: checkhints: unable to get root NS rrset from cache: not found

Hi,
        After upgrading to bind 9.5.1b I've begun to see the following
warning being logged on one of three dns server which are configured
identicaly?
" checkhints: unable to get root NS rrset from cache: not found"
Does anyone know is this is a  known problem Best Regards

Peter



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other than
the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.