On 9/12/2013 3:25 PM, Phil Fagan wrote:
Its a good point about the anycast; 99.999% should be expected.
A small choice of attitude-reflecting language. I expect 100.000% I'll accept 99.999% or better. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)
On 09/13/13 03:53, Larry Sheldon wrote:
On 9/12/2013 3:25 PM, Phil Fagan wrote:
Its a good point about the anycast; 99.999% should be expected. A small choice of attitude-reflecting language.
I expect 100.000%
I'll accept 99.999% or better.
It depends... define 'lost queries'. For example; is RRL included here or not (sometimes you want to deliberatly 'loose' queries). -- Marco
On 13-09-12 21:53, Larry Sheldon wrote:
I expect 100.000%
I'll accept 99.999% or better.
At these numbers, one has to start to count failover time. A "system" can be disaster tolerant but take 2 hours to recover fully, or it could also recover within a couple of seconds. It depends on architecture and available services. And in networking, you also need to consider internal and external routing update propagation times.
On 2013-09-13, at 16:01, Jean-Francois Mezei <jfmezei_nanog@vaxination.ca> wrote:
On 13-09-12 21:53, Larry Sheldon wrote:
I expect 100.000%
I'll accept 99.999% or better.
At these numbers, one has to start to count failover time.
Before really any part of this thread makes sense, you have to describe exactly what you mean by "available". Joe
On Fri, Sep 13, 2013 at 04:01:51PM -0400, Jean-Francois Mezei wrote:
On 13-09-12 21:53, Larry Sheldon wrote:
I expect 100.000%
I'll accept 99.999% or better.
At these numbers, one has to start to count failover time. A "system" can be disaster tolerant but take 2 hours to recover fully, or it could also recover within a couple of seconds. It depends on architecture and available services. And in networking, you also need to consider internal and external routing update propagation times.
from where? to where? what % of the Internet is _not_ reachable from my DNS service at any given time? why is that acceptable? and more importantly, who's job is it to fix/stablize the net so these "remote" locations can reach my DNS service? "we will answer 100% of the valid DNS queries we receive." /bill
* bmanning@vacation.karoshi.com (bmanning@vacation.karoshi.com) [Fri 13 Sep 2013, 22:16 CEST]:
from where? to where? what % of the Internet is _not_ reachable from my DNS service at any given time? why is that acceptable? and more importantly, who's job is it to fix/stablize the net so these "remote" locations can reach my DNS service?
"we will answer 100% of the valid DNS queries we receive."
Is this thread even about authoritative or recursive DNS? -- Niels. --
On Mon, Sep 16, 2013 at 06:36:22PM +0200, Niels Bakker wrote:
* bmanning@vacation.karoshi.com (bmanning@vacation.karoshi.com) [Fri 13 Sep 2013, 22:16 CEST]:
from where? to where? what % of the Internet is _not_ reachable from my DNS service at any given time? why is that acceptable? and more importantly, who's job is it to fix/stablize the net so these "remote" locations can reach my DNS service?
"we will answer 100% of the valid DNS queries we receive."
Is this thread even about authoritative or recursive DNS?
-- Niels.
Does it matter? /bill
participants (7)
-
bmanning＠vacation.karoshi.com -
Jean-Francois Mezei -
Joe Abley -
Larry Sheldon -
Marco Davids (Prive) -
Nick Hilliard -
Niels Bakker