Skip to content
AdminKit

DNS UPDATE (Dynamic DNS Update)

What is DNS UPDATE (Dynamic DNS Update)?

DNS UPDATE lets an authorized client add, delete or change individual records in a zone directly, without editing and reloading a zone file, and is normally restricted with TSIG or SIG(0) authentication. AdminKit's DNS Lookup tool shows a record's current live value, the same value an authorized or unauthorized Update actually changes.

By AdminKit team, Netbase JSC · Updated

DNS UPDATE, defined in RFC 2136 (document record at the IETF Datatracker) and listed as its own opcode in IANA’s DNS Parameters registry, is a DNS opcode that lets a client add, delete or replace individual resource records in an authoritative zone over the network, instead of an administrator editing a zone file and reloading the server by hand — useful for systems that need to publish their own current record, such as dynamic DNS clients or automated certificate issuance. Because an unauthenticated Update request would let anyone rewrite a zone’s records, RFC 3007 requires every secure Update message to carry a TSIG or SIG(0) signature the receiving server can verify against a shared key or public key before applying the change, separate from DNSSEC’s own signing of the resulting zone data. A nameserver that accepts Updates without this authentication, or with a weak or shared key, is effectively letting any client with network access silently rewrite its records — a quieter, more targeted risk than a full zone transfer. Server defaults differ, which is why the configuration is worth checking: PowerDNS Authoritative Server ignores DNS UPDATE messages unless dnsupdate=yes is set, and only from version 5.0.0 offers dnsupdate-require-tsig to refuse unsigned updates from an allowed address range. Microsoft’s Windows Server documentation on dynamic update notes that for standard primary zones dynamic updates aren’t secured, so any client update attempt succeeds, while Active Directory-integrated zones secure them with directory-based permissions.

AdminKit groups dNS UPDATE (Dynamic DNS Update) under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does DNS UPDATE let a client do that a normal DNS query can't?

It lets an authorized client add, delete or replace individual records in a zone over the network, instead of an administrator editing and reloading a zone file by hand.

Is DNS UPDATE secure by default?

No -- RFC 3007 requires a secure Update to carry a TSIG or SIG(0) signature the server verifies before applying any change; an unauthenticated Update would let anyone rewrite a zone's records.

Is DNS UPDATE's authentication the same thing as DNSSEC?

No -- TSIG/SIG(0) authenticates who may submit an Update request, while DNSSEC separately signs the resulting zone data so resolvers can verify it; the two protect different steps.

What does an unsafe DNS UPDATE configuration actually risk?

A nameserver accepting Updates without authentication, or with a weak or shared key, lets any client with network access silently rewrite its records -- a quieter, more targeted risk than a full zone transfer.