Man page - dnst-update(1)

Packages contas this manual

Manual

DNST-UPDATE(1) dnst DNST-UPDATE(1)

dnst-update - Send a dynamic update packet to update an IP (or delete all existing IPs) for a domain name

dnst update [OPTIONS] <DOMAIN NAME> <COMMAND>

dnst update [OPTIONS] <DOMAIN NAME> add <RRTYPE> [RDATA]...

dnst update [OPTIONS] <DOMAIN NAME> delete <RRTYPE> [RDATA]...

dnst update [OPTIONS] <DOMAIN NAME> clear <RRTYPE>

dnst update sends an RFC 2136 Dynamic Update message to the name servers for a zone to add, update, or delete arbitrary Resource Records for a domain name.

The message to be sent can be optionally authenticated using a given TSIG key.

dnst update [...] add adds the given RRs to the domain.

dnst update [...] delete deletes the given RRs from the domain. It can be used to delete individual RRs or a whole RRset.

dnst update [...] clear clears (deletes) all RRs of any type from the domain name.

<DOMAIN NAME>
The domain name of the RR(s) to update.

<COMMAND>
Which action to take: add, delete, or clear.

Class

Defaults to IN.


TTL in seconds or with unit suffix (s, m, h, d).

Is only used by the add command and is otherwise ignored.

Defaults to 3600.


The name server to send the update to.

By default, the update will be sent to the list of name servers fetched from the zone's NS RRset as per RFC 2136.


The zone the domain name belongs to (to skip a SOA query)

TSIG credentials for the UPDATE packet

Require that at least one RR with the given NAME and TYPE exists. This option can be provided multiple times, with format <DOMAIN_NAME> <TYPE> each, to build up a list of RRs.

If the domain name is relative, it will be relative to the zone's apex.

[aliases: --rrset]


Require that an RRset exists and contains exactly the RRs with the given NAME, TYPE, and RDATA. This option can be provided multiple times, each with one RR in zonefile format, to build up one or more RRsets that is required to exist. CLASS and TTL can be omitted.

If the domain name is relative, it will be relative to the zone's apex.

[aliases: --rrset-exact]


RRset does not exist. This option can be provided multiple times, with format <DOMAIN_NAME> <TYPE> each, to build up a list of RRs that specify that no RRs with a specified NAME and TYPE can exist.

If the domain name is relative, it will be relative to the zone's apex.

[aliases: --rrset-empty]


Name is in use. This option can be provided multiple times, with format <DOMAIN_NAME> each, to collect a list of NAMEs that must own at least one RR.

Note that this prerequisite is NOT satisfied by empty nonterminals.

If the domain name is relative, it will be relative to the zone's apex.

[aliases: --name-used]


Name is not in use. This option can be provided multiple times, with format <DOMAIN_NAME> each, to collect a list of NAMEs that must NOT own any RRs.

Note that this prerequisite IS satisfied by empty nonterminals.

If the domain name is relative, it will be relative to the zone's apex.

[aliases: --name-unused]


Print the help text (short summary with -h, long help with --help). Can also be used on the individual sub commands.

<RRTYPE>
The RR type to add or delete.

[RDATA]...
One or more RDATA arguments for add, and zero or more for delete.

Each argument corresponds to a single RR's RDATA, so beware of (shell and DNS) quoting rules.

Each RDATA argument will be parsed as if it was read from a zone file.

Examples:
dnst update some.example.com add AAAA ::1 2001:db8::
dnst update some.example.com add TXT '"Spacious String" "Another
string for the same TXT record"' '"This is another TXT RR"'


NLnet Labs

2024–2026, NLnet Labs

March 5, 2026 0.2.0-alpha1