These triggered the release of 9.7.2-P1
when we were rejecting these after tightening the response processing
to treat glue to answer responses as referrals to address the issue
of named return glue records from the parent zones rather than the
actual answers in the child zones.
Sorry I'm not
In message <4d2d0689.7010...@chrysler.com>, Kevin Darcy writes:
> The answers will be cached regardless of the setting of the AA flag. I
> would suspect that most -- or at least a large percentage -- of DNS
> queries made by endpoint clients are to upstream resolvers which don't
> happen to be
The answers will be cached regardless of the setting of the AA flag. I
would suspect that most -- or at least a large percentage -- of DNS
queries made by endpoint clients are to upstream resolvers which don't
happen to be authoritative for the zone(s) in question, so AA=0 is very
common in pra
I'm curious whether the domain in question had a DS in the parent zone?
On 11/01/11 4:52 PM, "Chris Thompson" wrote:
> On Jan 11 2011, Alexander Gall wrote:
>
>> It appears that NODATA responses for qtype=DNSKEY are not cached if
>> DNSSEC validation is enabled (tested with 9.7.2-P3). What is
On Jan 11 2011, Alexander Gall wrote:
It appears that NODATA responses for qtype=DNSKEY are not cached if
DNSSEC validation is enabled (tested with 9.7.2-P3). What is the
rationale behind this?
I confirm the effect (same release). Or rather, the NODATA does get cached,
as shown by a "!DNSKEY"
It appears that NODATA responses for qtype=DNSKEY are not cached if
DNSSEC validation is enabled (tested with 9.7.2-P3). What is the
rationale behind this?
--
Alex
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listi
6 matches
Mail list logo