Of
Kevin Darcy
Sent: Friday, October 12, 2012 12:48 PM
Cc: bind-users@lists.isc.org
Subject: Re: error (unexpected RCODE REFUSED) resolving
OK, so your nbc.com/A resolving error doesn't really have anything to do
with the nameservers you included in your original post.
It does appea
On Oct 12 2012, Kevin Darcy wrote:
OK, so your nbc.com/A resolving error doesn't really have anything to do
with the nameservers you included in your original post.
It does appear, however, that ns2.netbcp.net (205.173.93.213) is
refusing requests generally for the nbc.com domain:
And so is
2001:dc3::35
;; Query time: 147 msec
;; SERVER: 198.41.0.4#53(198.41.0.4)
;; WHEN: Mon Feb 18 13:29:18 2008
;; MSG SIZE rcvd: 615
"named.ca" 52L, 1892C
>>> "Kevin Darcy" ( mailto:k...@chrysler.com ) 10/12/2012
>>> 1:20 PM >>>
On 10/1
360 IN 2001:dc3::35
;; Query time: 147 msec
;; SERVER: 198.41.0.4#53(198.41.0.4)
;; WHEN: Mon Feb 18 13:29:18 2008
;; MSG SIZE rcvd: 615
"named.ca" 52L, 1892C
>>> "Kevin Darcy" 10/12/2012 1:20 PM >>>
On 10/12/2012 12:28 PM, James Tingle
ich we been actively deploying and testing). This has taken
away the log activity but I still get the error:
Oct 12 16:06:55 prod75-dns1 named[23866]: error (unexpected RCODE REFUSED)
resolving 'nbc.com/A/IN': 205.173.93.213#53
Exploring this more, almost all doma
On 10/12/2012 12:28 PM, James Tingler wrote:
Hello,
I'm getting what appears to be a common "error (unexpected RCODE
REFUSED) resolving" error. My research has lead me to disable IPv6
when starting the named service with "named -4" as it could be related
to IPv6 brok
Hello,
I'm getting what appears to be a common "error (unexpected RCODE REFUSED)
resolving" error. My research has lead me to disable IPv6 when starting the
named service with "named -4" as it could be related to IPv6 broken
connectivity (of which we been activ
7 matches
Mail list logo
