I have the same problem as described below. I´m running SuSE 6.4/bind8.2.2 for about 1/2 year without any problems. In the last weeks named is going down first about one time a week up to now every second day - and I can´t find any hint in the logs...any idea?
Have you tried more extensive logging or perhaps execution in debug mode? That will give you many more hints than are available from the default logging. cya, Tobias
Reckhard, Tobias wrote:
Have you tried more extensive logging or perhaps execution in debug mode? That will give you many more hints than are available from the default logging.
How can I put the extensive logging? Thank you. -- www.geekcode.com -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/cc/e/it d++ s+:+ a-- C++$ UL+++$ E++ W+++$ w--- O---- M V- PS PE+++ Y+ PGP- t+ 5 X++ R tv+ b++ DI-- D+ G e++$ h! r++ y++ ------END GEEK CODE BLOCK------ - A veces creo que hay vida en otros planetas, y a veces creo que no. En cualquiera de los dos casos, la conclusión es asombrosa (Carl Sagan) -----------------------------------------------------------------
* Hipolito A. Gonzalez M. (hgonzale@celularshow.com) [010402 04:59]:
How can I put the extensive logging? Thank you.
From named.conf(5) (Please read it):
logging { [ severity ( critical | error | warning | notice | info | \ debug [ level ] | dynamic ); ] }; ] You want 'debug'. -- -ckm
participants (3)
-
Christopher Mahmood
-
Hipolito A. Gonzalez M.
-
Reckhard, Tobias