RE: error (unexpected RCODE REFUSED) resolving

2012-10-13 Thread Frank Bulk
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

error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread James Tingler
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

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread Kevin Darcy
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

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread James Tingler
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

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread Kevin Darcy
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

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread James Tingler
...@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

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread Chris Thompson
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