Hello Stefan,
You are right, this change should be mentioned in the migration section and not only as an
improvement.
Thanks for this feedback,
Daniel
On 10/14/20 6:14 PM, Oto Stefan wrote:
Hallo everybody,
this is just a little remark concerning the 'knot' upgrade from 2.9.x to 3.0.x.
The 'update-owner-name' in the 'acl' section of the configuration file
can now be either the FQDN (with trailing dot) or a relative name to the zone, while it
used to be a domain name before (without
obligatory dot at the end). The documentation was updated correctly:
Doc for 2.9:
acl
- id: owner_type_rule
action: update
update-type: [A, AAAA, MX] # Updates are only allowed to update records of the
specified types
update-owner: name # The allowed owners are specified by the list on the next line
update-owner-name: [
a.example.com,
b.example.com,
c.example.com]
update-owner-match: equal # The owners of records in an update must be exactly
equal to the names in the list
Doc for 3.0:
acl
- id: owner_type_rule
action: update
update-type: [A, AAAA, MX] # Updates are only allowed to update records of the specified
types
update-owner: name # The allowed owners are specified by the list on the next line
update-owner-name: [a,
b.example.com.] # Non-FQDN names are relative to the effective
zone name
update-owner-match: equal # The owners of records in an update must be exactly equal to
the names in the list
However; I did not notice the subtle change and was struggling for a while to bring the
dynamic zone update into a working state again .
Maybe, this saves a little time to someone else.
Regards and thanks for a great piece of software,
Oto Stefan