Additional info - general: warning: checkhints: unable to find root NS
'b.root-servers.new' in hints
I cant seem to find where the .new coming from...
On Tue, Feb 3, 2015 at 2:07 PM, Linux Addict linuxaddi...@gmail.com wrote:
The named.ca seems good.
;; ANSWER SECTION:
.
Let me take a step back. The original problem is dig . would give
SERVFAIL instead of NOERROR. The . is pointed to named.ca which looks
normal.
On Tue, Feb 3, 2015 at 2:28 PM, Linux Addict linuxaddi...@gmail.com wrote:
Actually I tried +trace from BIND server itself and still get the same
Actually I tried +trace from BIND server itself and still get the same
answer. I did dig . +trace @localhost
; DiG 9.7.0-P1 . +trace @localhost
;; global options: +cmd
. 346239 IN NS i.root-servers.new.
. 346239 IN NS
There was nothing changed on the system since 2012. The behavior changed
all of sudden. I am just curious where dig got root servers like
b.root-servers.new..
On Tue, Feb 3, 2015 at 2:56 PM, Leonard Mills l...@yahoo.com wrote:
Let me take a step back. The original problem is dig .
would give
If I remember right, DIG does not know the root servers and asks the
local host to retrieve that information and a server at
172.27.254.11(which is RFC 1918 address space) gave you that answer.
Is your machine/shop setup with private root servers?
Lyle
On 2/3/2015 12:50 PM, Linux Addict
The named.ca seems good.
;; ANSWER SECTION:
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS
On Tue, Feb 03, 2015 at 01:50:14PM -0500, Linux Addict wrote:
I do dig . +trace and the results seem show .new servers. This is
causing SERVFAIL for root query. Any ideas?
dig . +trace
Contact the person who runs the resolver at 172.27.254.11 and report the
problem about the root hints. dig
172.27.254.11 is giving you that info with the .new name servers. You
need to ask whomever manages that server.
Look at this line from your +trace output:
Received 405 bytes from 172.27.254.11#53(172.27.254.11) in 1 ms
Lyle
On 2/3/2015 1:13 PM, Linux Addict wrote:
Additional info - general:
Let me take a step back. The original problem is dig .
would give SERVFAIL instead of NOERROR.
The . is pointed to named.ca which looks normal.
Without source code changes to your tools and/or replacement
hints files . invariably points to the root servers to be used by the
(possibly
Mukund Sivaraman wrote:
On Tue, Feb 03, 2015 at 01:50:14PM -0500, Linux Addict wrote:
I do dig . +trace and the results seem show .new servers. This is
causing SERVFAIL for root query. Any ideas?
dig . +trace
Contact the person who runs the resolver at 172.27.254.11 and report the
Thanks all for your inputs!!
On Tue, Feb 3, 2015 at 4:39 PM, Robert Edmonds edmo...@mycre.ws wrote:
Mukund Sivaraman wrote:
On Tue, Feb 03, 2015 at 01:50:14PM -0500, Linux Addict wrote:
I do dig . +trace and the results seem show .new servers. This is
causing SERVFAIL for root query.
11 matches
Mail list logo