DNS record types
Add or edit a record
- Open Zones and select the zone.
- Choose Add Record. To change an existing record, open it and choose Edit.
- Choose a type, enter the name and value, set the TTL, and add a priority for MX or SRV records.
- Save. If your role cannot approve its own changes, submit the proposal and ask an authorised reviewer to approve it under Pending Changes.
The record list lets you filter, sort, select several records, and use bulk actions. The available actions depend on your role.
Record names and targets
Enter the record name as a fully qualified name without a final dot. For
example, use www.example.dk for a record in example.dk; do not enter just
www or www.example.dk.. The name is not relative to the zone.
Target names in record values follow the form’s guidance. For CNAME and SRV targets, add a final dot to make an external hostname unambiguous. A target inside the current zone can be entered as a subdomain or full name; without a final dot the form appends the current zone where appropriate. Check the preview/help text for the selected type before saving.
Common types
| Type | Typical use | Example value |
|---|---|---|
| A | IPv4 address | 192.0.2.10 |
| AAAA | IPv6 address | 2001:db8::10 |
| CNAME | Alias to another hostname | target.example.net. |
| MX | Mail server; set the priority in the Priority field | mail.example.dk |
| TXT | Verification and policy text, including SPF and DKIM | v=spf1 include:example.net -all |
| SRV | Service location; set priority separately and enter weight, port and target as directed by the form | 5 5060 sip.example.dk |
| CAA | Which certificate authorities may issue certificates | 0 issue "letsencrypt.org" |
| HTTPS / SVCB | Service connection hints | 1 . alpn="h2,h3" |
| PTR | Reverse lookup name | host.example.dk |
The application enables record types from its current DNS configuration, so the type selector is the definitive list. Some additional types may be available. DNSSEC records are managed by the DNSSEC workflow; SOA and nameserver records are system-managed and are not added through the record editor.
TTL and validation
TTL is the number of seconds a resolver may cache an answer. Use a shorter TTL ahead of a planned change only if you have time for the previously published TTL to expire. Restore your usual TTL after the change is stable. A low TTL does not force caches to discard answers they already hold.
The form validates values for the selected type and shows errors beside the relevant field. For example, MX and SRV use priority, CAA flags are constrained, and a CNAME cannot share its owner name with other record types. A save can also be held for review or prevented by the organisation’s resource limit.
After a change is applied, query the authoritative nameservers shown for your zone. Recursive resolvers may continue to return the old answer until their caches expire.
PTR records and reverse DNS
A PTR record maps an IP address back to a host name. It belongs in the reverse
zone for the address, such as an in-addr.arpa zone for IPv4 or an ip6.arpa
zone for IPv6. The network that controls the address range must delegate that
reverse zone to the authoritative nameservers that serve it. Creating a PTR
inside an ordinary forward zone does not make it visible in reverse DNS.
Generate a PTR from an A or AAAA record
From a zone’s record list, choose Generate PTR beside an A or AAAA record. Review the preview, which shows the PTR name, target, and reverse zone. If the reverse zone does not exist, the application offers to create it. The action may be held for approval or create a disabled reverse zone or PTR record if a resource limit is reached. Check the warning before confirming. If a PTR already exists for that address, generating another replaces the existing mapping.
You can also choose the zone’s Auto PTR policy when creating or editing a forward zone:
- Never — do not create PTR records automatically.
- Always — create or update PTR records for A/AAAA records and create reverse zones when needed.
- Only if domain exists — create PTR records only when the reverse zone already exists.
The policy affects automatic PTR handling for records in that zone. It does not control the explicit Generate PTR action. A template can change a zone’s Auto PTR policy when you apply it; review that setting, especially when applying a template to several zones.
To review a zone’s A and AAAA records together, open the zone’s more-actions menu and choose Generate PTR Records. The review page shows which records already have a PTR; they are skipped by default. Select the records you want to process and confirm. Resource limits or approval requirements are shown before the operation completes.
Review or manage reverse zones
Reverse zones appear under Zones in the in-addr.arpa or ip6.arpa list.
Open the reverse zone to review its PTR records. You can edit or remove a PTR
there like other records, subject to the zone’s permission and approval rules.
Deleting a reverse zone removes its PTR records, but it does not change who
delegates the IP range’s reverse DNS.
From a reverse zone’s more-actions menu, Generate PTR Records can also create PTR entries for an IPv4 range. Review the address range and preview; existing PTRs are skipped by default. Range generation is not available for IPv6 reverse zones because of their much larger address space.