Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread James Tingler
ou have enough working authoritative nameservers for the domain, so it'll continue to resolve for you... - Kevin On 10/12/2012 1:35 PM, James Tingler wrote: I don't think

Re: error (unexpected RCODE REFUSED) resolving

2012-10-12 Thread James Tingler
M.ROOT-SERVERS.NET. 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 P

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). Thi

Re: Error Resolving / EDNS

2012-09-19 Thread James Tingler
r.net'?) after disabling EDNS Sep 19 15:25:27 PROD55-DNS2 named[3676]: success resolving 'ns3.timewarner.net/' (in 'timewarner.net'?) after disabling EDNS >>> "Carsten Strotmann" 9/19/2012 10:45 AM >>> Hello James, "James T

Error Resolving / EDNS

2012-09-19 Thread James Tingler
After a BIND server (BIND 9.7.0-P2-RedHat-9.7.0-6.P2.el5_7.4) rebuild and a thorough review of the ASA firewall configuration (to allow UDP 53 > 512), I continue to get resolution errors and/or extreme resolution delays caused by an unknown factor but as evidence by EDNS disabling for misc exter