-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Jun 12, 2015 at 03:21:26PM +0100, Gerard Hooton wrote:
> Hi All,
> I already sent that was but before I subscribed to the list.
>
> I have included the following in my named.conf
>
> logging {
> channel bind_log {
> file "/var/log/bind/bind.log" versions 3 size 5m;
> severity info;
> print-category yes;
> print-severity yes;
> print-time yes;
> };
> category default { bind_log; };
> category update { bind_log; };
> category update-security { bind_log; };
> category security { bind_log; };
> category queries { bind_log; };
> category lame-servers { null; };
> };
>
> However I get the following error
>
> Jun 12 14:21:52 scoil named[7161]: loading configuration from
> '/etc/bind/named.conf'
> Jun 12 14:21:52 scoil named[7161]: /etc/bind/named.conf.log:1:
HERE^^^^^^^^^^^^^^^
> unknown option 'logging'
> Jun 12 14:21:52 scoil named[7161]: loading configuration: failure
> Jun 12 14:21:52 scoil named[7161]: exiting (due to fatal error)
>
> I have the following
> 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux
> BIND 9.8.4-rpz2+rl005.12-P1
Just a shot in the dark: your /etc/bind/named.conf seems to include
/etc/bind/named.conf, which itself most probably has a "logging"
stanza itself.
Perhaps this error message is Bind9's idiosyncratic way to tell
you that it doesn't like to see two logging entries?
Anyway, it might seem better for the sysadmin's sanity to modify
the logging stuff in /etc/bind/named.conf.log
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlV67SQACgkQBcgs9XrR2kYyJwCeIiuXnuFi6iovhwKtkPc6y2gL
Lh8An3zOpa3ZlZa6GWPAi/WA9QNRHXas
=Nz8Q
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150612143100.ga23...@tuxteam.de
