Add 64-self to 48-self update policy rules

These rules are intended to allow ISP customers to add delegations
in the IPv6 reverse tree that correspond to the IPv6 prefix delegations
that they have recieved from the ISP.  This is similar to the
existing 6to4-self rule which but for the other nibble boundaries
in common use.
This commit is contained in:
Mark Andrews
2025-03-06 15:10:10 +11:00
parent b652d5327c
commit db4c5dfdbc
6 changed files with 137 additions and 24 deletions
+23 -3
View File
@@ -7349,7 +7349,7 @@ records are also written to the zone's filename.
Each rule grants or denies privileges. Rules are checked in the order in
which they are specified in the :any:`update-policy` statement. Once a
message has successfully matched a rule, the operation is immediately
granted or denied, and no further rules are examined. There are 16 types
granted or denied, and no further rules are examined. There are 23 types
of rules; the rule type is specified by the ``ruletype`` field, and the
interpretation of other fields varies depending on the rule type.
@@ -7405,11 +7405,12 @@ records are also written to the zone's filename.
send
EOF
The ruletype field has 18 values: ``name``, ``subdomain``, ``zonesub``,
The ruletype field has 23 values: ``name``, ``subdomain``, ``zonesub``,
``wildcard``, ``self``, ``selfsub``, ``selfwild``, ``ms-self``,
``ms-selfsub``, ``ms-subdomain``, ``ms-subdomain-self-rhs``, ``krb5-self``,
``krb5-selfsub``, ``krb5-subdomain``, ``krb5-subdomain-self-rhs``,
``tcp-self``, ``6to4-self``, and ``external``.
``tcp-self``, ``6to4-self``, ``64-self``, ``60-self``, ``56-self``,
``52-self``, ``48-self`` and ``external``.
``name``
With exact-match semantics, this rule matches when the name being updated is identical to the contents of the ``name`` field.
@@ -7496,6 +7497,25 @@ records are also written to the zone's filename.
.. note::
It is theoretically possible to spoof these TCP sessions.
``64-self``, ``60-self``, ``56-self``, ``52-self``, ``48-self``
These allow records at reverse IPv6 names at the specified
nibble boundary to be updated if a TCP request comes from
an IPv6 address in the matching prefix. These are intended
to allow ISP customers to add delgation records when using
DHCPv6 prefix delegations or when prefix delegation is used
within a site.
::
grant * 64-self * NS DS;
grant ISP-DHCPv6-SERVER-KEY zonesub ANY;
Which will allow customers to add delegation records and the
DHCPv6 server to clean up when the lease expires.
.. note::
It is theoretically possible to spoof these TCP sessions.
``external``
This rule allows :iscman:`named` to defer the decision of whether to allow a given update to an external daemon.
+1 -1
View File
@@ -58,7 +58,7 @@ zone <string> [ <class> ] {
sig-signing-type <integer>;
sig-validity-interval <integer> [ <integer> ]; // obsolete
update-check-ksk <boolean>; // obsolete
update-policy ( local | { ( deny | grant ) <string> ( 6to4-self | external | krb5-self | krb5-selfsub | krb5-subdomain | krb5-subdomain-self-rhs | ms-self | ms-selfsub | ms-subdomain | ms-subdomain-self-rhs | name | self | selfsub | selfwild | subdomain | tcp-self | wildcard | zonesub ) [ <string> ] <rrtypelist>; ... } );
update-policy ( local | { ( deny | grant ) <string> ( 48-self | 52-self | 56-self | 60-self | 64-self | 6to4-self | external | krb5-self | krb5-selfsub | krb5-subdomain | krb5-subdomain-self-rhs | ms-self | ms-selfsub | ms-subdomain | ms-subdomain-self-rhs | name | self | selfsub | selfwild | subdomain | tcp-self | wildcard | zonesub ) [ <string> ] <rrtypelist>; ... } );
zero-no-soa-ttl <boolean>;
zone-statistics ( full | terse | none | <boolean> );
};