could not start named.conf
Adriatik Allamani
aallamani at ert.gov.al
Tue Aug 14 07:13:34 UTC 2007
Hi
I checked the named.conf file with:
/usr/sbin/named-checkconf
And it comes out with error:
/etc/named.conf:12: 'directory' redefined near 'directory'
That I think it was the problem of redefined 'directory' again in the
configuration.
I removed the line '12'. Now the named-checkconf shows no error.
But it does not start again
Aug 14 08:04:29 ns1 named[6033]: starting BIND 9.2.4 -u named
Aug 14 08:04:29 ns1 named[6033]: using 2 CPUs
Aug 14 08:04:29 ns1 named[6033]: loading configuration from
'/etc/named.conf'
Aug 14 08:04:29 ns1 named[6033]: listening on IPv4 interface lo,
127.0.0.1#53
Aug 14 08:04:29 ns1 named[6033]: listening on IPv4 interface eth0,
217.24.249.76#53
Aug 14 08:04:29 ns1 named[6033]: command channel listening on
127.0.0.1#953
Aug 14 08:04:29 ns1 named[6033]: couldn't open pid file 'named.pid':
Permission denied
Aug 14 08:04:29 ns1 named[6033]: exiting (due to early fatal error)
The permission thing again?
below is the named.conf file.
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
// Process environment
pid-file "named.pid"; // Put pid file in working
directory
Thanks
Adriatik Allamani
On Mon, 2007-08-13 at 17:08 +0100, Niall O'Reilly wrote:
> On 13 Aug 2007, at 16:04, Adriatik Allamani wrote:
>
> > I added the line:
>
> Did you put it in the 'options' block, like this extract from my
> running system?
>
> options {
>
> // Process environment
> // directory "/local/var/named/run"; // Working directory
> directory "/run"; // Working directory (chroot'd)
> pid-file "named.pid"; // Put pid file in working
> directory
>
> // more options ...
>
> };
>
> Perhaps you need to read the documentation ... ?
>
> /Niall
More information about the bind-users
mailing list