>> The brackets were wrong and we should have checked that obj was true.
> The patch you provided makes the log message go away. The bind9 service
> appears to be working normally, and named-checkconf produces no output.
> Thanks. Jeff.
FYI. The patch for /lib/bind9/check.c provided earlier in
> The brackets were wrong and we should have checked that obj was true.
The patch you provided makes the log message go away. The bind9 service appears
to be working normally, and named-checkconf produces no output. Thanks. Jeff.
___
Please visit https
In message <7610864823c0d04d89342623a3adc9de54c4a...@hopple.countryday.net>, "S
pain, Dr. Jeffry A." writes:
> For bind 9.9.3 build on Ubuntu 12.04LTS x64, I see log messages, for example,
> "/etc/bind/named.conf.local:4: zone 'jaspain.biz': missing 'file' entry" for
> each slave zone configured
> Have you looked carefuly enough, and to the correct file if there is no
> missed character that makes the configuration invalid?
> Have you run named-checkconf with and without the given file as parameter?
The log message is new since bind-9.9.2-P2 with no changes to the configuration
files. T
On 02.06.13 14:27, Spain, Dr. Jeffry A. wrote:
For bind 9.9.3 build on Ubuntu 12.04LTS x64, I see log messages, for
example, "/etc/bind/named.conf.local:4: zone 'jaspain.biz': missing 'file'
entry" for each slave zone configured for inline signing. The file clause
is, in fact, present in the con
For bind 9.9.3 build on Ubuntu 12.04LTS x64, I see log messages, for example,
"/etc/bind/named.conf.local:4: zone 'jaspain.biz': missing 'file' entry" for
each slave zone configured for inline signing. The file clause is, in fact,
present in the configuration file, for example:
zone "jaspain.biz
6 matches
Mail list logo
