Knot DNS merge requestshttps://gitlab.nic.cz/knot/knot-dns/-/merge_requests2024-02-27T12:42:36+01:00https://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1650implemented keytag-modulo option2024-02-27T12:42:36+01:00Libor Peltanimplemented keytag-modulo option3.4Daniel SalzmanDaniel Salzmanhttps://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1596khost: parse resolve.conf file and parse 'search' domains2023-10-23T11:04:44+02:00Jan Hákjan.hak@nic.czkhost: parse resolve.conf file and parse 'search' domainshttps://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1135Nsec dname cmp zero2021-04-02T10:53:32+02:00Libor PeltanNsec dname cmp zeroThis "solves" the situation when records in zone are wrongly ordered because of `knot_dname_lf` with connection to `\000`.
The user is warned when creating NSEC tree, when owner with `\000` is present.
NSEC tree creation/update fails, ...This "solves" the situation when records in zone are wrongly ordered because of `knot_dname_lf` with connection to `\000`.
The user is warned when creating NSEC tree, when owner with `\000` is present.
NSEC tree creation/update fails, if this directly affects zone ordering.
This does not solve many situations when there is collision of names after `knot_dname_lf` applied!Daniel SalzmanDaniel Salzman