Hi Olafur,
Thanks for this report. It's a bug in Knot configuration processing.
Will be fixed soon.
If you want to check your zone/configuration, you can use:
knotc checkzone ...
knotc checkconf
Regards,
Dan
On 01/31/2014 10:47 PM, Olafur Gudmundsson wrote:
I started to play with the dnssec signing features in
Knot.
I had this in my .conf file
B-100.tld { file "B-100.zone"; …. }
In the B-100.zone file I had
$ORIGIN B-100.tld.
I get
Jan 31 16:27:32 bigredone knot[31315]: [error] Zone 'B-100.tld.': mismatching
origin in the zone file.
Jan 31 16:27:32 bigredone knot[31315]: [error] Failed to load zone 'B-100.tld.'.
When I changed to
$ORIGIN b-100.tld.
Same error
When I changed the conf line for B-100 to b-100
zone got loaded,
I when I changed Origin to upper case but kept the lower case in conf file then zone was
loaded.
Summary: conf file requires zone name to be lower case, origin can be either case.
(not documented)
I do not think this what users expect.
Either respect the case that users present or downcase both zone name and name on $ORIGIN
line
Also I would be great to have knot-checkzone command that one can use to verify the
syntax of zone
with output to standard output.
Olafur
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users