djbdns
[Top] [All Lists]

Re: dnscache bug, or ... ?

To: david@stults.com
Subject: Re: dnscache bug, or ... ?
From: Charlie Brady <charlieb-dns@e-smith.com>
Date: Wed, 31 Jan 2007 09:58:00 -0500 (EST)
Cc: dns@list.cr.yp.to
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-djbdns@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list dns@list.cr.yp.to
In-reply-to: <49198.64.122.164.12.1170186066.squirrel@stults.com>
Mailing-list: contact dns-help@list.cr.yp.to; run by ezmlm
On Tue, 30 Jan 2007 david@stults.com wrote:

> See the example below for what I'm referring to.  Even if I were to move
> the domain integra.net to a new provider, and the root servers were
> appropriately updated, I could keep my dnscache returning the wrong
> answers indefinitely as long as two conditions are met:
> 
> 1.  The old DNS servers respond authoritatively
> 2.  I query dnscache prior to TTL expiration on the NS records asking for
> the domain SOA.

Yes, AIUI, this is a bug in the DNS RFCs. Domain redelegation cannot work
reliably if the old DNS servers are not decommissioned. The old servers 
are rarely under the same administrative control as the new servers.

--
Charlie


<Prev in Thread] Current Thread [Next in Thread>