Hello.
I seem to remember seeing something about DNSSEC validation not working
when a BIND server is used both to serve the DNSSEC signed zone
authoritatively, and as a resolver? Unfortunately, I haven't managed to
find this information again, and now I'm wondering if it was all in my
head.
(Resending it here, didn't mean to reply just to you Alan)
On 1/6/2011 3:38 AM, Eivind Olsen wrote:
(Yes, I know it's best practice to combine the authoritative + recursive
functionality)
[...] it's NOT best [...]
Yep, I knew that. Embarassing of me to miss that slightly important
NOT-word
just FYI
In message 20101229090538.17173t2lbw1zw...@mail.junc.org, Benny Pedersen
writes:
post to bind-users@lists.isc.org not to bind-us...@isc.org
On 30.12.10 10:02, Mark Andrews wrote:
To: Benny Pedersen m...@junc.org
From: Mark Andrews ma...@isc.org
Subject: Re: bind9 cache
Date:
Greetings,
Upgraded today from BIND 9.2.4 to BIND 9.7.0-P2-RedHat-9.7.0-5.P2.el6_0.1.
Pretty much copied the named.conf file from one to the other.
We are a slave for a three other sites, two I download the zones OK, one I
get REFUSED since the upgrade.
I thought permissions or config error on my
On Thu, 6 Jan 2011, jim wrote:
Upgraded today from BIND 9.2.4 to BIND 9.7.0-P2-RedHat-9.7.0-5.P2.el6_0.1.
Pretty much copied the named.conf file from one to the other.
We are a slave for a three other sites, two I download the zones OK, one I
get REFUSED since the upgrade.
Check your BIND
Hi Jeremy,
Thanks for the reply, I am using allow-transfer { ... }
I just heard back about five minutes ago for the admin and they had removed
our site as a secondary.
The RCODE 5 was right on the money telling me what was going on and the
logging
failed while receiving responses: REFUSED
and
On 01/06/2011 11:30 PM, Gary Wallis wrote:
(Some dig output lines deleted to keep short)
Why does this not work (but below next dig with +trace seems to imply
that it should?):
The delegation looks invalid:
147.95.81.in-addr.arpa. 172800 IN NS ns1.theplanet.com.
In message 4d26508c.7090...@gmail.com, Gary Wallis writes:
(Some dig output lines deleted to keep short)
Why does this not work (but below next dig with +trace seems to imply
that it should?):
More modern version of dig report the error BAD (HORIZONTAL) REFERRAL.
If 147.95.81.in-addr.arpa
8 matches
Mail list logo
