checkhints: unable to get root NS rrset from cache: not found
Peter Davies
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
Mark Andrews
What do you have in your hints file?
What do you get if you run "dig ns . @<address>" where
<address> are the addresses in the hints file.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_A...@isc.org
Peter Davies
I loaded a new version from the net same time I upgraded bind .
When I started receiving the checkhints warning I remove the ip6 entries
- but that didn't help.
Here's the content of the hints file minus comments
/Peter
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 192.228.79.201
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 199.7.83.42
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
Mark Andrews <Mark_A...@isc.org>
Sent by: Mark_A...@isc.org
20-08-2008 14:48
To
Peter Davies/SCA/CSC@CSC
cc
bind-...@isc.org
Subject
Re: checkhints: unable to get root NS rrset from cache: not found
Mark Andrews
Peter Davies
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
pdav...@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" <tsn...@rim.com>
20-08-2008 14:59
To
Peter Davies/SCA/CSC@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-use...@isc.org [mailto:bind-use...@isc.org] On
Behalf Of Peter Davies
Sent: Wednesday, August 20, 2008 8:30 AM
To: bind-...@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.
Todd Snyder
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.