| To: | "djbdns list" <dns@list.cr.yp.to> |
|---|---|
| Subject: | Re: dnscache bug, or ... ? |
| From: | "Malte Tancred" <malte-os-f029a5739161d738eb59f48b162a199d@tancred.com> |
| Date: | 30 Jan 2007 22:27:16 +0100 |
| 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 |
| References: | <49198.64.122.164.12.1170186066.squirrel@stults.com> |
On Jan 30, 2007, at 20.41, david@stults.com wrote: [...] See the example below for what I'm referring to. Even if I were to movethe 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 But they shouldn't, right? See <URL:http://cr.yp.to/djbdns/run-server.html#move-zone>, point 4: "Make the same changes on the old servers. This is important because caches can continue talking to the old servers for any length of time; caches are under no obligation to double-check with the parent servers." Regards, Malte |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | dnscache bug, or ... ?, david |
|---|---|
| Next by Date: | Re: dnscache bug, or ... ?, Charlie Brady |
| Previous by Thread: | dnscache bug, or ... ?, david |
| Next by Thread: | Re: dnscache bug, or ... ?, Charlie Brady |
| Indexes: | [Date] [Thread] [Top] [All Lists] |