bind-9.2.4-16.EL4 problem

Mark Andrews Mark_Andrews at isc.org
Thu Sep 7 21:46:27 UTC 2006



> Well, Thank you
> But why is my bind behaving like this, i thought it might be caused by
> the firewall DNS inspection and i removed it from the PIX but still the
> same problem happens, i defined the edns packet size to be 512 and
> still no luck??!!
> when i restart the named everything resolves fine for a while and then
> it returns to the same behavior of resolving most internet but some are
> not resolving,
> also when performing nslookup it doesn't give me timedout as if i was
> denied querying it gives me server failed!!
> 
> i would appreciate any help with this regard

	Most probably because there is as misconfiguration with the
	delegation of the zone which hold the names you are looking
	up.  Without specifics it's hard to do more than speculate.
 
> Elzey, Blaine A (Blaine) wrote:
> > 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 Behal
> f 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 ar
> e 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/in
> it.d/named restart Stopping named: [  OK  ] Starting named: failed already ru
> nning [root at localhost /]#  /etc/init.d/named start Starting named: [  OK  ]
> >
> > and after that every thing even names were not resolving begin resolving fi
> ne!
> > 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"; }; };
> 
> 
--
ISC Training!  October 16-20, 2006, in the San Francisco Bay Area,
covering topics from DNS to DHCP.  Email training at isc.org.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list