On Mon, Nov 17, 2008 at 4:20 AM, James Hess <[EMAIL PROTECTED]> wrote:
> One of the secondary/tertiary recursive resolvers may hand the client
> a cached response that had been obtained before the registrar took any
> action.

Yes, and that'd  make a good case for the good old ops practice of
dialing down the TTL for a while before any NS change is made.

--srs

Reply via email to