restarting named...takes a long long time ???

Brad Knowles brad.knowles at skynet.be
Fri Aug 24 22:32:10 UTC 2001


At 7:11 PM +0200 8/24/01, Frank Benady wrote:

>  named serves about 4000 zones on the server.
>
>  The pb : it takes 20 up to 30 minutes to restart named with the following
>  command
>
>  /usr/sbin/named -c /etc/named/named.conf
>
>   Is it normal ? Is it because of the 4000 db.files it has to read ?

	Yup, this is normal with 4000 zones.  If you upgrade to the 
latest release of BIND 9 and install a version built with 
multi-threading enabled (assuming your kernel version and compiler 
are compatible with doing so), it will start answering queries 
immediately while background threads continue to load the zones.

>  Moreover, when named restarts the syslogd start eating up all the ressources
>  on the server.
>  Do I have to stop syslod before restarting named ?

	This is also normal, as named is syslogging a boatload of stuff. 
If you set up logging channels that go directly to files (instead of 
to syslog), then you can avoid all the syslog overhead, and have BIND 
write the log output on its own.  IIRC, BIND 9 gives you some better 
tools for managing this process than BIND 8.

-- 
Brad Knowles, <brad.knowles at skynet.be>

H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7
Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes
MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il
wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP
dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/
uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA


More information about the bind-users mailing list