RE: named problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Turns out I lied. Remming the first acl did help, then removing the 192.168.0.0/16; is what did it. Sorry for being stupid... -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use iQA/AwUBOqzy0BeamMdwy9

named problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am having problems with a named that I built from sources... Not SRPM, but tar.xx. I can do lookups all day on the box that it's running on. However, when I try to lookup from another on my LAN, it fails. Can't find server, NXDOMAIN blah blah... Any

Re: Named problems

hehe, perhaps you need to put a line 'FILES=512' in your config.sys ? On Thu, 2 Apr 1998, Nick Koston wrote: > I keep getting these errors when I restart/start named. It seems > only to work when the system is just starting up and then go balistic > adter it has booted completely. My gues

Named problems

I keep getting these errors when I restart/start named. It seems only to work when the system is just starting up and then go balistic adter it has booted completely. My guess is after the system has finished booting it has to many files open (have to raise a max open files limit somewhere