named -u named is using 49676 kB

Is this too much? it appears to be using more memory than any other process. I know my name server shouldnt be using 49MB of memory. :(

It shouldn't use that much memory. Try upgrade named .. maybe there's a memory leak problem with the version you're using.

Originally posted by drhonk
It shouldn't use that much memory. Try upgrade named .. maybe there's a memory leak problem with the version you're using.

Thanks I will see if that fixes the prob.

Also check for scripts which use domain lookups... a common one for that is a script which checks a load of domains at once to see if they're available yet (can't remember the script name).

I have named on one of my servers restarted every day, because it's on a machine with only 128MB of RAM, and it occasionally spikes for some reason.

- Matt

The new bind version 9 is a memory hog. It uses much more memory than previous versions. It has a larger cache by default, and is more cpu intensive. Ours is currently using 90 MB of RAM, and it has been running for 2 weeks since last restart.

The amount of memory being used depends on the # of domains in the DNS, and the # of requests it serves. We saw a 150-200% increase in memory usage when we upgraded from bind 8 to 9.

- John C.