17 Nov
2008
17 Nov
'08
11 a.m.
On Mon, 2008-11-17 at 05:15 +0530, Suresh Ramasubramanian wrote:
On Mon, Nov 17, 2008 at 4:20 AM, James Hess <mysidia@gmail.com> 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.
That would work only if Godaddy was considering suspending it for greater than TTL time before actually suspending them...it takes the same time to dial-down TTL (old TTL time) then change it, as it does to just change it outright. -- Jeremy Jackson Coplanar Networks (519)489-4903 http://www.coplanar.net jerj@coplanar.net