Of
Kevin Darcy
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 appea
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 is
Actually, I'm getting mostly no resolution for these sites. Ever so often I
will get resolution after multiple nslookup attempts.
Another weird thing that happened today is with the "named -4" trigger, my
internal resolution broke. I killed the named service and started bind
normally so no
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:
$ dig nbc.com +buf=4096 +norec @ns2.netbcp.ne
I don't think that I am. I only define internal forwarders for internal zones
as needed. For my root hint, standard configuration:
Named.conf
zone "." {
type hint;
file "named.ca";
Named.ca:
; <<>> DiG 9.5.0b2 <<>> +bufsize=1200 +norec NS . @a.root-servers.net
;; global optio
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
6 matches
Mail list logo
