Hi Guys, 1. Distribution: Red Hat Linux release 9 (Shrike) 2. Kernel: Linux host.itres.com 2.4.20-30.9smp #1 SMP Wed Feb 4 20:36:46 EST 2004 i686 i686 i386 GNU/Linux 3. Bind version: bind-devel-9.2.1-16 ypbind-1.11-4 kdebindings-3.1-6 bind-9.2.1-16 redhat-config-bind-1.9.0-13 kdebindings-devel-3.1-6 bind-utils-9.2.1-16
I have an issue with bind. Named is dying on me, since I upgraded to RH9 - clean new install. I have searched on the internet for a reported bug or something, but the only reference I found was to a DoS attack on bind for RH7.1, 7.2, and 7.3. The recommendation was to upgrade to bind 9.2.1 or higher. As you can see, I'm running what appears to be the latest version of bind and friends. There's nothing on the redhat's support website which would point to my problem. I have in a band-aid solution in place right now, which runs a cron script, every minute, to check if named is running; if not running 'start'. Even though any request for name services would have to wait for at least a minute for a response, one minute can seem an eternity when waiting... This is /var/log/messages when the script runs if named is dead. l 13 12:12:01 hostname named[15258]: starting BIND 9.2.1 -u named Jul 13 12:12:01 hostname named[15258]: using 2 CPUs Jul 13 12:12:01 hostname named: named startup succeeded Jul 13 12:12:01 hostname named[15258]: loading configuration from '/etc/named.conf' Jul 13 12:12:01 hostname named[15258]: no IPv6 interfaces found Jul 13 12:12:01 hostname named[15258]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 13 12:12:01 hostname named[15258]: listening on IPv4 interface eth0, 192.168.173.142#53 Jul 13 12:12:01 hostname named[15258]: command channel listening on 127.0.0.1#953 Jul 13 12:12:01 hostname named[15258]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Jul 13 12:12:01 hostname named[15258]: zone 173.168.192.in-addr.arpa/IN: loaded serial 2004070801 Jul 13 12:12:01 hostname named[15258]: zone itres.com/IN: loaded serial 2004070803 Jul 13 12:12:01 hostname named[15258]: zone localhost/IN: loaded serial 42 Jul 13 12:12:01 hostname named[15258]: running There's no trace of what happens before named dies or what is killing it, or even if it's a suicidal activity. Any ideas where I can look for such info. I would be interested if any of you have seen, experience, or have any suggestion how to even look for indications what causing the problem. Thanks in advance. Rafael. -- J. Rafael SÃnchez Systems Administrator Itres Research Limited (p) 403.250.9944 (f) 403.250.9916 _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
