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 appear, however, that ns2
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 actively deploying and testing
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 broken connectivity (of which we
prod75-dns1 named[23866]: error (unexpected RCODE REFUSED)
resolving 'nbc.com/A/IN': 205.173.93.213#53
Exploring this more, almost all domains I'm having problems with (as discovered
through dig) is related to this forwarder:
nationalmap.gov. 5M IN NS rdsdns5.ultradns.net. nationalmap.gov. 5M IN NS
SIZE rcvd: 615
named.ca 52L, 1892C
Kevin Darcy k...@chrysler.com 10/12/2012 1:20 PM
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
...@chrysler.com ( mailto:k...@chrysler.com ) 10/12/2012
1:20 PM
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
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
Hello Mark Andrews,
Am 2010-08-04 08:32:29, hacktest Du folgendes herunter:
Basically you need to complain to the administators for xensource.com
to get the delegation cleaned up or the server configured.
OK... done!
xensource.com is delegated to 68.156.138.136 but that server is refusing
Hello,
since today morning (~06:30 CEST) I get several 1.000 errors like:
[ '/var/log/named.log' ]
Aug 3 10:12:39 dns1 named[26425]: 03-Aug-2010 10:12:39.951 lame-servers: info:
unexpected RCODE (REFUSED) resolving 'lists.colo.xensource.com
:
[ '/var/log/named.log' ]
Aug 3 10:12:39 dns1 named[26425]: 03-Aug-2010 10:12:39.951 lame-servers: i=
nfo: unexpected RCODE (REFUSED) resolving 'lists.colo.xensource.com/A/IN': =
68.156.138.136#53
Basically you need to complain to the administators
10 matches
Mail list logo