Hello,
strike my last email, after a short discussion we decided to allow
usage of '@' even when no $ORIGIN directive is used. The fix is now in
our "development" branch in git repository (see our webpage for more
info) and will be present in upcoming Knot version 1.1. Thanks for your
report!
Regards,
Jan.
On Wed, 2012-07-04 at 19:57 +0900, Koh-ichi Ito wrote:
Hello again. Here's another one.
I noticed that zone data contains relative notation such as
'@' but no $ORIGIN causes error.
knotc checkzone says:
-----
kohi@lars[1]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc checkzone example1.jp
[sudo] password for kohi:
2012-07-04T19:52:19.603883+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:52:19.615871+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:52:19.631618+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
-----
And knotc compile says:
-----
kohi@lars[2]% /usr/bin/sudo /proj/knot-1.0.6/sbin/knotc compile
2012-07-04T19:54:02.023025+09:00 Using '/proj/knot-dns/etc/knot.conf' as default
configuration.
2012-07-04T19:54:02.039299+09:00 Parsing file '/proj/dns/namedb/example1.jp',
origin 'example1.jp.' ...
2012-07-04T19:54:02.051637+09:00 [error] /proj/dns/namedb/example1.jp:3: @ used, but no
$ORIGIN specified.
2012-07-04T19:54:02.052790+09:00 [error] /proj/dns/namedb/example1.jp:11: Zone file does
not contain SOA record!
2012-07-04T19:54:02.053653+09:00 [error] Compilation of 'example1.jp.' failed,
knot-zcompile return code was '1'
-----
It complains even though it knows that "origin 'example1.jp.' ...".
Is this behavior by design policy? Or I wish it to be
enhanced.
Best regards,
Koh-ichi Ito
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users