Manage UAPP DNS Records
Edit account-owned DNS records with type-specific fields, revision protection and legacy migration, and download zone or YAML exports from UAPP.
From DNS Zones, open Manage DNS for the intended domain. Confirm the account and zone before editing.
Add a record
Click Add Record, choose the type, enter the relative Name, fill its content and additional options, review TTL, then click Save Record. The form changes its labels and fields for the selected type; do not paste a complete zone-file line.
Use the step-by-step addition guide for Name/target rules, TTL, save conflicts and verification. Common record examples cover A, AAAA, CNAME, MX, TXT, NS, SRV and CAA. Advanced record fields explain all remaining supported types and exact numeric/digest requirements.
Standard fields
The table shows Type, Name, Content, TTL and actions. Add/Edit requires a type, record name, type-appropriate content and TTL. Use @ for the zone apex or a relative name such as www. TTL is in seconds; the visible range is 0–2147483647, with additional DNS validation applied server-side.
Supported choices are A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, TLSA, PTR, AFSDB, DNAME, DS, HINFO, LOC, NAPTR, RP, SVCB and HTTPS. SOA records are excluded from the UAPP editable list; the service manages the SOA serial automatically.
Type-specific fields
| Type | Content and additional fields |
|---|---|
| A / AAAA | IPv4 or IPv6 address. |
| CNAME / DNAME / NS / PTR | Appropriate alias, nameserver or pointer target. |
| TXT | Text value; use the text editor rather than treating it as an address. |
| MX | Mail-server target and priority. |
| SRV | Service target, priority, weight and port. |
| CAA | Policy value, flags and tag. |
| TLSA | Association data, usage, selector and matching type. |
| AFSDB | Server target and subtype. |
| DS | Digest, key tag, algorithm and digest type. |
| HINFO | CPU description and operating system. |
| LOC | Location coordinates. |
| NAPTR | Replacement target, order, preference, flags, service and regular expression. |
| RP | Responsible mailbox and TXT domain. |
| SVCB / HTTPS | Service target, priority and optional service parameters. |
Type-specific numeric ranges and relationships are validated beyond the basic form controls. For SVCB/HTTPS, alias mode uses priority zero without service parameters; service mode uses positive priority. Preserve DNS alias and apex relationships across the whole zone.
Save, delete and refresh
Choose Add or Edit, complete the applicable fields and save. Delete opens a confirmation showing record name, type and value; review all three before confirming. Copying record content does not change it.
Writes use the loaded zone revision. If another update makes it stale, refresh and reconcile the current records before retrying. If a save succeeds but the updated list cannot load, refresh rather than repeating the mutation.
Legacy zones are identified before normal record editing and can require explicit migration. Preserve the existing zone and review conversion feedback. Do not assume arbitrary legacy syntax can be edited as version-two data without conversion.
ACME challenge information is separate from ordinary records. Preserve certificate-validation behavior when editing related names. Demo mode blocks mutations; ownership, session identity and backend permissions are checked.
Download the zone
The export menu offers Download Zone File and Download YAML for an owned zone supported by the current exporter. Zone File renders DNS zone text; YAML preserves the stored structured representation. Export is a download, not an import, and does not change delegation or publish a replacement zone.
Keep exports private where they reveal internal service details. Legacy or invalid data can prevent export; review the response rather than treating a failed download as a backup.
Verify authoritative service after editing
A valid saved record can still point to the wrong host or conflict with another service's expectations. Check authoritative answers and affected web, mail and certificate behavior, allowing for cached TTLs.