[79861] in North American Network Operators' Group
Re: Memory leak cause of Comcast DNS problems
daemon@ATHENA.MIT.EDU (Fergie (Paul Ferguson))
Sun Apr 17 12:40:56 2005
From: "Fergie (Paul Ferguson)" <fergdawg@netzero.net>
Date: Sun, 17 Apr 2005 16:39:08 GMT
To: fw@deneb.enyo.de
Cc: nanog@merit.edu
Errors-To: owner-nanog@merit.edu
Regardless of whether it actually _was_ a memory leak,
or not, it appears that the impact was on a rather
large enough scale.
- ferg
-- Florian Weimer <fw@deneb.enyo.de> wrote:
| The maximum amount of memory to use for the server's cache, in
| bytes. [...] The default is unlimited, meaning that records are
| purged from the cache only when their TTLs expire.
The number of complaints I've heard that "DNS resolvers eat *so* much
memory" suggests that few people tweak the default configuration. 8-(
However, it's unlikely that this was the cause of Comcast's problems
because DNS cache overflows would have an impact on a much larger
scale.
--
"Fergie", a.k.a. Paul Ferguson
Engineering Architecture for the Internet
fergdawg@netzero.net or fergdawg@sbcglobal.net
ferg's tech blog: http://fergdawg.blogspot.com/
