bind-9.2.4-16.EL4 problem
Elzey, Blaine A (Blaine)
belzey at lucent.com
Wed Sep 6 19:39:15 UTC 2006
Sometimes named takes more time to shutdown than the time between stop and start commands in your named script. Try adding a sleep 1 or sleep 3 between the stop and start.
Blaine Elzey
LWS VitalQIP
Lucent Technologies
BElzey at Lucent.com <mailto:BElzey at Lucent.com>
(610) 722-7976
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf Of Shaheen
Sent: Wednesday, September 06, 2006 4:59 AM
To: comp-protocols-dns-bind at isc.org
Subject: bind-9.2.4-16.EL4 problem
Hi,
Am facing a really weird problem with mentioned version of bind.
my network scenario is as follows
3 bind-9.2.4-16.EL4 on FC5 behind PIX firewall, Most of internet queries are successful but some fails and log file does not show errors.
when i try to restart named i get the following [root at localhost /]# /etc/init.d/named restart Stopping named: [ OK ] Starting named: failed already running [root at localhost /]# /etc/init.d/named start Starting named: [ OK ]
and after that every thing even names were not resolving begin resolving fine!
why is this happeneing,
my primary named.conf looks like this
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
version "Get Lost";
allow-query { any; };
allow-recursion { localhost; trusted; };
blackhole { badguys; };
notify yes;
datasize default;
max-cache-size 800000000;
allow-transfer { secondaries; };
also-notify {x.x.x.x; y.y.y.y;}; // all zones
allow-notify { secondaries; };
recursive-clients 30000;
pid-file "named.pid";
};
logging {
category lame-servers { null; };
channel "default_debug" {
file "/var/log/named/named.log" size 5m;
severity critical;
};
};
controls {
inet x.x.x.x allow { x.x.x.x; } keys { "rndckey"; }; };
More information about the bind-users
mailing list