5.3 Securely Authenticate Update Forwarding


A secondary authoritative name server is allowed to accept zone updates on behalf of the primary name server, and forward them to the master name server, where the zone file can be updated. In this case, the authentication of the dynamic updates is configured with the allow-update-forwarding option. The update requests must be securely authenticated with a key identifier, rather than by an IP address. The key identifier may specify a TSIG key, a GSS-TSIG, or a SIG(0) key.


Of course, allowing unauthenticated updates to a zone should not be allowed. It is necessary for the secondary authoritative name server to carefully authenticate the update request before sending it on to the primary name server, to prevent malicious DNS updates be propagated via the secondary server.


Modify any allow-update-forwarding options to specify a securely generated TSIG or SIG(0) key identifier used by the DHCP server.

Default Value:

Dynamic updates are disabled by default.

See Also


Item Details


References: 800-53|IA-5, 800-53|IA-5(1), CSCv6|9, CSCv7|16.4

Plugin: Unix

Control ID: 18ffb6ed948aaddaff76fcf933c99c67870534ee7f89962c65f1e8034e383f3b