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


To: Jim Reid <Jim.Reid@nominum.com>
cc: DNS Operations <dnsop@cafax.se>
From: Pekka Savola <pekkas@netcore.fi>
Date: Wed, 23 Oct 2002 15:03:12 +0300 (EEST)
In-Reply-To: <18533.1035373038@shell.nominum.com>
Sender: owner-dnsop@cafax.se
Subject: Re: anycast

On Wed, 23 Oct 2002, Jim Reid wrote:
> >>>>> "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?

I believe the discussion was also about those servers possibly having 
ccTLD and gTLD data.

Imagine a situation where you could get every xxx.yyy name without going 
outside of your AS?

For the first lookup in the root servers, the opmization is .. "premature" 
to quote D. Knuth.. :-)

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords

#----------------------------------------------------------------------
# To unsubscripbe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list