[Re: [lug] Memory problem]

[Nate Duehr]

Even if you're not authoritative for anything, the server still builds
up a cache of every query you make and holds them until the TTL expires.
Heh... that's why it's called a "caching" nameserver!  :) :) :)

So are there a lot of people using your CounterStrike server?  Does it
log connections by name?  (i.e. would it have enough traffic to build a
cache pretty quickly?)

Any DNS server, caching or authoritative is going to cache up the entire
root zone also, but that's trivial... Once it contacts a server in your
root.cache (or whatever you call your cache startup file), it will then
ask for all the root NS records and hold those in RAM.  Then it will
cache all the glue records from the root down to the zones you look up
and at least the SOA record for the zones you go to and any individual
records you ask for.  (MX, A, PTR, etc.)

So the cache can get pretty big pretty quick.  You can look in DNS &
BIND for more info on how to read the output of ndc memstats to see if
BIND is using up a whole lot of memory... I think ndc stats also gives a
generic memory usage, but I can't remember, and there's no named on this
laptop.  :)

Glad to have pointed out the memory directives.  I went digging through
the isc.org documentation one late night when I was thinking about DNS
and what all I could do to my servers (on a little learning spree about
DNS) and while I was looking for DNSSEC info and other stuff, I ran
across those.

Have a nice evening...

On Tue, Nov 28, 2000 at 04:23:54PM -0700, Justin wrote:
> On this particular machine I just run a caching nameserver so there are no
> zones or anything that it is authorative for. I have another seperate box that
> does all the dns requests and another box that is the secondary. I think the
> BIND service on this particular box rarely if ever gets used. But since you
> mentioned those BIND directives I may use them on my other BIND servers  :)  I
> didn't know about them, hehe.

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.