Skip to Content
Browse documentation

Manage DNS Records

Add, edit, delete and export WAP DNS records, including advanced record fields, SOA controls and revision conflicts.

Open Network & DNS → DNS → View All DNS Zones, then click Manage on the intended zone.

Workspace and access

The manager shows the domain, owner and selected template. Use Refresh, record-type filters, quick filters, search and pagination to inspect records. Copy controls copy the displayed content. The ACME Challenges panel, when present, displays data managed by certificate operations.

The current record API requires the authenticated WAP root identity and unique account ownership for the zone. If a session expires, sign in again. Do not guess an owner or retry a permission failure with another account's URL.

Upgrade a legacy zone

A legacy zone initially shows Upgrade Zone rather than the record workspace. The panel states that a backup is kept. Upgrade deliberately, wait for completion and inspect the migrated records before editing. If migration fails, read the error and review the DNS log; do not discard the old data.

Common fields

FieldValue
TypeSupported DNS record type.
Name@ for the zone apex, or a relative name such as www.
ContentAddress, target, text or other data appropriate to the type.
TTLCache lifetime in seconds, from 0 through 2147483647. New records start with the zone's default TTL.

For TXT, enter the text without surrounding quotes. Target-hostname fields accept an optional trailing dot in the UI. IPv4 and IPv6 content must match the selected A or AAAA type.

Type-specific fields

TypeContent and additional fields
AIPv4 address.
AAAAIPv6 address.
CNAME, DNAMEAlias target hostname.
MXMail-server hostname; Priority.
TXTText value in the multiline field.
NSNameserver hostname.
SRVService target; Priority, Weight, Port.
CAAPolicy value; Flags, Tag.
TLSAHexadecimal certificate association data; Usage, Selector, Matching Type.
PTRPointer target hostname.
SOAPrimary Nameserver; Responsible Mailbox, Refresh, Retry, Expire, and TTL. Serial and Minimum TTL are displayed read-only.
AFSDBAFS database server hostname; Subtype.
DSHexadecimal digest; Key Tag, Algorithm, Digest Type.
HINFOCPU Description; Operating System.
LOCLocation Coordinates, including direction and altitude as required by DNS syntax.
NAPTRReplacement Target; Order, Preference, Flags, Service, Regular Expression.
RPResponsible Mailbox email address, or . for none; TXT Domain.
SVCB, HTTPSService Target, or .; Priority and optional Service Parameters.

For SOA enter the responsible mailbox as an email address. The serial updates automatically on save. You can edit the existing SOA, but cannot add another SOA, delete it or change its name/type.

For SVCB/HTTPS, priority 0 selects alias mode with no parameters; priority 1 or greater selects service mode. Enter optional parameters in DNS presentation syntax, such as alpn="h2,h3" port=443. Other numeric options have type-specific limits; use the values required by the service rather than relying on the generic browser maximum.

Add or edit

  1. Export a copy before substantial changes.
  2. Click Add Record, or the record's edit control.
  3. Select its type and complete the visible fields.
  4. Click Save Record and read the result.
  5. Inspect the refreshed records and verify the authoritative answer.

Validation checks the candidate zone and record relationships. Resolve reported conflicts rather than creating duplicate or incompatible records. A record edit changes DNS data; it does not create the target mail server, web service or address allocation.

Delete

Click a record's delete control, review its name, type and value, then confirm deletion. Cancel leaves the record unchanged. SOA has no delete control.

Check service dependencies

Removing DNS records can disrupt websites, mail, certificate validation and service discovery. Keep required NS, mail-policy and service records until their replacement is ready. Do not manually remove managed certificate challenge data as part of routine cleanup.

Export

Use Export Zone → Download Zone File for the rendered zone or Download YAML for stored zone data. Treat exports as administrative data. This manager does not offer an import or restore button; downloading a file does not itself provide a tested recovery procedure.

Concurrent edits and failures

Changes include the loaded zone revision. If another operation changes the zone, the server reports The zone has changed. Refresh the records before saving. Refresh, compare the current values and reapply the intended change. Do not keep resubmitting stale edits.

The service validates and deploys changes through the DNS backend. If it reports a deployment error, inspect the saved and served state and DNS log before retrying. Local success does not prove public resolver caches have expired or registrar delegation is correct.