<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/12/2012 12:28 PM, James Tingler
wrote:<br>
</div>
<blockquote cite="mid:50780CC8.2E62.00CF.0@CONTR.NETL.DOE.GOV"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19298">
<div>Hello,</div>
<div> </div>
<div>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 "<span
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE:
12pt; mso-fareast-font-family: 'Times New Roman'">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:</span></div>
<div><span style="FONT-FAMILY: 'Times New Roman','serif';
FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></span> </div>
<div>Oct 12 16:06:55 prod75-dns1 named[23866]: error (unexpected
RCODE REFUSED) resolving 'nbc.com/A/IN': 205.173.93.213#53</div>
<div> </div>
<div>Exploring this more, almost all domains I'm having problems
with (as discovered through dig) is related to this forwarder:</div>
<div>
<pre>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.</pre>
<pre>linkedin.com, nbc.com, nationalmap.gov</pre>
</div>
</blockquote>
nbc.com is not hosted on those nameservers:<br>
<br>
nbc.com. 86400 IN NS pdns1.ultradns.net.<br>
nbc.com. 86400 IN NS pdns2.ultradns.net.<br>
nbc.com. 86400 IN NS pdns3.ultradns.org.<br>
nbc.com. 86400 IN NS pdns4.ultradns.org.<br>
nbc.com. 86400 IN NS pdns5.ultradns.info.<br>
nbc.com. 86400 IN NS
pdns6.ultradns.co.uk.<br>
nbc.com. 86400 IN NS ns1.netbcp.com.<br>
nbc.com. 86400 IN NS ns2.netbcp.net.<br>
<br>
Neither is linkedin.com.<br>
<br>
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.<br>
<br>
<br>
<blockquote cite="mid:50780CC8.2E62.00CF.0@CONTR.NETL.DOE.GOV"
type="cite">
<div>
<pre>Note - I'm also seeing plenty of lame server and EDNS errors. </pre>
</div>
</blockquote>
Those are fairly normal.<br>
<br>
- Kevin<br>
</body>
</html>