Bugzilla – Bug 301
unbound-checkconf cannot parse interface '0.0.0.0@5353'
Last modified: 2010-03-22 10:39:47 CET
unbound-checkconf can't parse addresses with @port properly. This doesn't seem to affect unbound which seems to start and run with the interface line that checkconf errors out on.
colo-ns1 etc # unbound-checkconf /etc/unbound/unbound.conf
 unbound-checkconf[17805:0] fatal error: cannot parse interface specified as '0.0.0.0@5353'
colo-ns1 etc # unbound -h
usage: unbound [options]
start unbound daemon DNS resolver.
-h this help
-c file config file to read instead of /etc/unbound/unbound.conf
file format is described in unbound.conf(5).
-d do not fork into the background.
-v verbose (more times to increase verbosity)
linked libs: event 1.4.13-stable, ldns 1.6.4, OpenSSL 0.9.8l 5 Nov 2009
linked modules: python validator iterator
Thanks for the report. Fixed in svn trunk r2057.
Best regards, Wouter