[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Pekka Savola <pekkas@netcore.fi>
Cc: DNS Operations <dnsop@cafax.se>
From: Jim Reid <Jim.Reid@nominum.com>
Date: Wed, 23 Oct 2002 04:37:18 -0700
In-Reply-To: Message from Pekka Savola <pekkas@netcore.fi> of "Wed, 23 Oct 2002 11:03:37 +0300." <Pine.LNX.4.44.0210231101460.27150-100000@netcore.fi>
Sender: owner-dnsop@cafax.se
Subject: Re: anycast

>>>>> "Pekka" == Pekka Savola <pekkas@netcore.fi> writes:

    Pekka> Having almost all of your customers' DNS lookups take 10 ms
    Pekka> instead of 100 or 200 ms may also be of some value.

Unlikely. There are very few situations where DNS latency *really*
matters. The occassional lookup to a root server -- which is all a
well behaved name server should need to do -- is not one of them. You
seem to be overlooking the fact that name servers cache. The first
lookup of some name could take 200ms (or more) but subsequent lookups
of that name will be answered from the server's cache for the RR's TTL
value which is probably measured in hours or days. Against that
background, the sort of nano-optimisation you appear to be advocating
is pointless. Why care about shaving 100ms or so off *one* DNS lookup
out of thousands or millions of lookups? What is the justification for
engineering an "optimal" solution for just that one lookup?
#----------------------------------------------------------------------
# To unsubscripbe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list