From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Description of problem: named.conf with logging { category "default" { "vse"; "syslog"; }; channel "syslog" { syslog daemon; severity dynamic; }; }; prevents named startup. Jan 28 13:19:44 www named[15451]: logging channel 'vse': not found Jan 28 13:19:44 www named[15451]: configuring logging: not found Jan 28 13:19:44 www named[15451]: loading configuration: not found Jan 28 13:19:44 www named[15451]: exiting (due to fatal error) named-checkconf remains silent about this misconfiguration. Version-Release number of selected component (if applicable): bind-9.2.1-16 How reproducible: Always Steps to Reproduce: 1.up2date -i bind 2.add logging in named.conf as shown in description 3.named-checkconf 4.service named start Additional info:
Yes - the current named-checkconf won't complain about errors in zone files or views either. The new bind-9.3.0, to which we will be migrating shortly, does return non-zero for zone file or view errors - but still not logs. This is because only the actual server code goes so far as to attempt to USE the logging configuration, when these errors are found . This issue has been reported to the upstream maintainers where it would be more appropriately fixed. Once the new bind-9.3.0 named-checkconf is released, which is radically different from the curent named-checkconf, we can revisit this issue.