On Thu, 30 Jan 2003 13:26:27 +0000, Daniel Lorch <[EMAIL PROTECTED]> said:
> hi,
>> There is a nice paper studying the impact of TTL values on DNS traffic
>> and response times: "DNS Performance and the Effectiveness of
>> Caching", by Jaeyeon Jung, Emil Sit, Hari Balakrishnan, Robert Morris
>> (yes, *that* Morris :-), Internet Measurement Workshop 2001 (IMW 2001):
>> 
>> http://nms.lcs.mit.edu/papers/dns-imw2001.ps.gz

> Interesting read, thanks alot. I now understand what circumstances lead
> to negative caching.

> Got more of these .ps.gz's ? :)

This paper was presented at the 2001 ACM SIGCOMM Internet Measurement
Workshop.  I went to the 2002 one last November (in Marseilles) and
there were many excellent papers there too.  The proceedings,
including full PDF of all papers, can be found here:

http://www.icir.org/vern/imw-2002/proceedings.html

Some papers are a bit on the theoretical side, but many are actually
quite interesting for network operators.  There were two papers in the
"DNS" session, but only the second one really talks about DNS
performance observations.

>> The gist is that caching at the delegation points (NS records and
>> their associated A records) is what provides most benefit, while the
>> impact of low-TTL A records isn't that bad.

> I experienced problems with TTLs around 300, where domains from time
> to time suddenly didn't resolve anymore. I couldn't trace the cause
> for this and it wasn't easily reproducible, but having a higher TTL
> solved this problem for me. 

What often causes intermittent problems like this is when one of the
alternative delegation paths to the name is misconfigured,
i.e. lame-delegated or so.  Then you can resolve the name when you
happen to use the "good" path, but after a timeout you may use the
"bad" path and encounter a SERVFAIL somewhere (a timeout would be
harmless).

This is just one reason why you should be very careful to keep your
delegations up to date, monitor all your secondaries for proper
resolution of your names and proper zone updates, and ALWAYS inform
your authoritative name server (slave or other) operators when you
move a zone AWAY from them, and make sure the zone is removed from the
old server(s).
-- 
Simon.
----------------------------------------------
[EMAIL PROTECTED] Maillist-Archive:
http://www.mail-archive.com/swinog%40swinog.ch/

Reply via email to