Thanks all for your inputs!!
On Tue, Feb 3, 2015 at 4:39 PM, Robert Edmonds 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. Any ideas?
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 rep
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 wrote:
> >Let me take a step back. The original problem is "dig ."
> > would give SERVFA
>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
(possib
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 wrote:
> Actually I tried +trace from BIND server itself and still get the same
> answer. I did "dig .
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 c
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:
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 wrote:
> The named.ca seems good.
>
> ;; ANSWER SECTION:
> . 518400 IN
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.
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 B.
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 wrote
I do dig . +trace and the results seem show .new servers. This is causing
SERVFAIL for root query. Any ideas?
dig . +trace
; <<>> DiG 9.7.0-P1 <<>> . +trace
;; global options: +cmd
. 348510 IN NS b.root-servers.new.
. 348510 IN NS
2011/7/9 Lyle Giese :
>
> qq.com zone is the parent to the subdomain www.qq.com, so it has to have
> knowledge of the name servers for the www.qq.com subdomain. That is how a
> recursive name server finds www.qq.com.
>
Do you mean the reference?
I don't think the first case is answering with a
requested but not available
> >
> > ;; QUESTION SECTION:
> > ;www.qq.com.IN NS
> >
> > ;; AUTHORITY SECTION:
> > qq.com. 86400 IN SOA ns1.qq.com.
> > webmaster.qq.com. 1293074536 300 600 86400 86400
> &
; ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;www.qq.com.IN NS
>
> ;; AUTHORITY SECTION:
> qq.com. 86400 IN SOA ns1.qq.com.
> webmaster.qq.com. 1293074536 300 600 86400 86400
>
> ;; Qu
webmaster.qq.com. 1293074536 300 600 86400 86400
;; Query time: 7 msec
;; SERVER: 121.14.73.115#53(121.14.73.115)
;; WHEN: Sat Jul 9 08:59:07 2011
;; MSG SIZE rcvd: 78
I have two questions against the two dig info above.
First, why ns1.qq.com (which is the authority nameserver for the zone
6 300 600 86400 86400
;; Query time: 7 msec
;; SERVER: 121.14.73.115#53(121.14.73.115)
;; WHEN: Sat Jul 9 08:59:07 2011
;; MSG SIZE rcvd: 78
I have two questions against the two dig info above.
First, why ns1.qq.com (which is the authority nameserver for the zone
of qq.com, not www.qq.com) returns the
Tech W. wrote:
--- On Mon, 18/5/09, Mark Andrews wrote:
From: Mark Andrews
Subject: Re: dig info
To: "Tech W."
Cc: bind-users@lists.isc.org
Received: Monday, 18 May, 2009, 10:35 PM
In message <980168.77226...@web15605.mail.cnb.yahoo.com>,
"Tech W." writes:
--- On Mon, 18/5/09, Mark Andrews wrote:
> From: Mark Andrews
> Subject: Re: dig info
> To: "Tech W."
> Cc: bind-users@lists.isc.org
> Received: Monday, 18 May, 2009, 10:35 PM
>
> In message <980168.77226...@web15605.mail.cnb.yahoo.com>,
> "Tech
In message <980168.77226...@web15605.mail.cnb.yahoo.com>, "Tech W." writes:
>
> Sometime I dig a domain name, it returns the results below:
>
> ;; reply from unexpected source: 59.42.52.246#59721, expected 211.66.80.167#5
> 3
> ;; reply from unexpected source: 59.42.52.246#59721, expected 211.66
Sometime I dig a domain name, it returns the results below:
;; reply from unexpected source: 59.42.52.246#59721, expected 211.66.80.167#53
;; reply from unexpected source: 59.42.52.246#59721, expected 211.66.80.167#53
;; reply from unexpected source: 59.42.52.246#59721, expected 211.66.80.167#53
This one is a badly configured load balancer. The lookup sometimes
succeeds as the glue from the parent zone is used. This however
is not guarenteed to be the case and explict queries for the addresses
of the nameservers will detect the problems causing subsequent
--- On Sun, 12/4/09, Gregory Hicks wrote:
> From: Gregory Hicks
> Subject: Re: help on strange dig info
> To: bind-users@lists.isc.org, tech...@yahoo.com.cn
> Received: Sunday, 12 April, 2009, 3:33 PM
>
> > I digged a domain name as below:
> >
> > r.
> Date: Sun, 12 Apr 2009 15:22:42 +0800 (CST)
> From: "Tech W."
> Subject: help on strange dig info
> To: bind-users@lists.isc.org
>
>
> Hello,
>
>
> I digged a domain name as below:
>
> r...@dev1:~# dig www.csfunds.com.cn
>
> ; <<&
Hello,
I digged a domain name as below:
r...@dev1:~# dig www.csfunds.com.cn
; <<>> DiG 9.5.0-P2 <<>> www.csfunds.com.cn
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23283
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0
;;
25 matches
Mail list logo
