North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: IP failover/migration question.

  • From: infowolfe
  • Date: Tue Jun 27 12:17:28 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AoQnUKCULDjZ+IwYTuHB78hjdq5dk+sriIwGtFVqveRexlkyvBnIhmmHipyGg1qU4lUN/g75HD4l/E2Wt7L8wkAayhNw0riDR8nW00t6gX6VVNhuTEuZpyhimKViesD8ES1wcPwRPiHFrD+4411Yja2FP5ia9rU6IqcQ8qQAswo=

On 6/27/06, [email protected] <[email protected]> wrote:
On Tue, 27 Jun 2006 14:51:30 BST, Andy Davidson said:
> Popular web browsers running on popular desktop operating systems
> also display extra-long dns cache time 'bugs'.

A well known fact, which leads right into your next comment...

> 24 hours + outage whilst stale dns disappears will never do in
> internet retail.

And yet, with 90% of the net implementing the "will never do" scenario,
we manage to get a lot of internet retail done anyhow.  I'm obviously going
to need a *lot* more caffeine to sort through that conundrum....

Could you imagine slashdot, amazon or google going down for 24 hours?
I think there would be panic in the streets.

Uptime might not matter for small hosts that do mom and pop websites
or so-called "beta" blog-toys, but every time Level3 takes a dump,
it's my wallet that feels the pain. It's actually a rather frustrating
situation for people who aren't big enough to justify a /19 and an
AS#, but require geographically dispersed locations answering on the
same IP(s).