AAAA type query invalidates A records in name server cache
Bill Owens
owens at nysernet.org
Tue Jul 19 16:48:44 UTC 2011
On Tue, Jul 19, 2011 at 04:58:53PM +0200, mailsecurity wrote:
> All,
>
> anyone experiencing the same behavior?
I hope so, because that's the correct behavior. Dell's nameserver is broken:
http://tools.ietf.org/html/rfc4074
Common Misbehavior Against DNS Queries for IPv6 Addresses - May 2005
4.2. Return "Name Error"
This type of server returns a response with RCODE 3 ("Name Error") to
a query for an AAAA RR, indicating that it does not have any RRs of
any type for the queried name.
With this response, the stub resolver may immediately give up and
never fall back. Even if the resolver retries with a query for an A
RR, the negative response for the name has been cached in the caching
server, and the caching server will simply return the negative
response. As a result, the stub resolver considers this to be a
fatal error in name resolution.
fpdns says that Dell's servers are BIND, wonder if that's accurate, and if so, how ancient a release, to have this bug?
Bill.
More information about the bind-users
mailing list