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 been actively deploying and
testing). This has taken away the AAAA 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 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 rdsdns1.ultradns.net.
nationalmap.gov. 5M IN NS rdsdns2.ultradns.net.
nationalmap.gov. 5M IN NS rdsdns6.ultradns.net.
nationalmap.gov. 5M IN NS rdsdns3.ultradns.net.
nationalmap.gov. 5M IN NS rdsdns4.ultradns.net.
linkedin.com, nbc.com, nationalmap.gov
nbc.com is not hosted on those nameservers:
nbc.com. 86400 IN NS pdns1.ultradns.net.
nbc.com. 86400 IN NS pdns2.ultradns.net.
nbc.com. 86400 IN NS pdns3.ultradns.org.
nbc.com. 86400 IN NS pdns4.ultradns.org.
nbc.com. 86400 IN NS pdns5.ultradns.info.
nbc.com. 86400 IN NS pdns6.ultradns.co.uk.
nbc.com. 86400 IN NS ns1.netbcp.com.
nbc.com. 86400 IN NS ns2.netbcp.net.
Neither is linkedin.com.
I hope you're not trying to use authoritative nameservers as
"forwarders" in the strict BIND sense. If you have full Internet
connectivity, there's really no reason to be forwarding at all.
Configure your root hints and be happy.
Note - I'm also seeing plenty of lame server and EDNS errors.
Those are fairly normal.
- Kevin
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
