Add DNS Records in UAPP
Add a DNS record through UAPP DNS Manager with the correct relative Name, target or text content, TTL and type-specific fields, then verify the saved result.
Open Hosting → DNS → DNS Zones, then Manage DNS for the intended zone. Click Add Record. This adds one record to an existing zone; Add DNS Zone creates a zone instead.
Before adding
Confirm the zone belongs to your account and is where authoritative DNS is served. If the domain uses an external authoritative provider, editing this server's copy alone does not update that provider. Have the exact record values from the service you are configuring and preserve an export before substantial changes.
If the manager displays Upgrade Zone, the legacy zone must be migrated before normal editing. Demo mode blocks adding records. SOA is managed by the service and is not an available UAPP record type.
Add a record
- Check the domain shown at the top of DNS Manager.
- Click Add Record and select Type. A is initially selected.
- Enter Name, relative to this zone.
- Enter the type's address, target, text or other content.
- Set TTL and complete all additional fields displayed for that type.
- Click Save Record once and wait for the result.
- Find the saved record in the refreshed table and check its name, content, TTL and options.
- Verify the authoritative DNS answer and the affected service separately.
Shared fields
| Field | What to enter |
|---|---|
| Type | One of the 19 supported types. Choosing it changes the content label and additional fields. |
| Name | Required: @ for the zone apex, or a relative name such as www, _dmarc or _sip._tcp. |
| Content | Required; its label changes to IPv4 Address, Mail Server, Text Value or the appropriate type-specific label. |
| TTL | Required integer seconds, 0–2147483647. Initially filled from the zone's default TTL. |
| Additional fields | Depends on Type; see the common and advanced field guides below. |
For a zone named example.com:
| Name entered | DNS owner produced |
|---|---|
@ | example.com |
www | www.example.com |
shop.api | shop.api.example.com |
_acme-challenge | _acme-challenge.example.com |
*.shop | *.shop.example.com |
Do not enter www.example.com in Name for that zone: the editor treats it as relative and can create www.example.com.example.com. A trailing dot is not the form's owner-name format. Names are normalized for case and internationalized labels, with DNS label and full-name length validation.
Hostname targets versus addresses and text
For CNAME, MX, NS, SRV and other hostname-target types, enter a full hostname such as mail.example.net, without a URL scheme, port or path. A trailing dot is optional in this panel and is normalized by the backend. A short target such as mail is treated as an absolute hostname, not expanded to mail.example.com.
A/AAAA require an address, not a hostname. TXT uses a multiline text box: paste the logical value without zone-file surrounding quotes or a complete IN TXT line. Keep MX priority, SRV port and other options in their own fields rather than combining them with Content.
- Common records and examples covers A, AAAA, CNAME, MX, TXT, NS, SRV and CAA.
- Advanced record fields covers TLSA, PTR, AFSDB, DNAME, DS, HINFO, LOC, NAPTR, RP, SVCB and HTTPS.
Validation and conflicts
Records with the same Name and Type form an RRset and must use the same TTL. Different A or MX values can share that Name/Type if they are valid and not duplicates. Adding an identical record is rejected.
A CNAME must be the only record at its owner, with only one target. An apex CNAME is incompatible with the zone's required apex SOA/NS records. The zone must retain at least one apex NS. Only one SPF TXT policy per owner and one DMARC policy at _dmarc are allowed by the zone validator. Check existing records and policy-generated content before adding another.
Resolve conflicts before replacing records
Do not delete working records merely to make a new value pass validation. Confirm the service's intended change, preserve current values and consider other uses of the same name. Certificate challenges are also managed separately in the ACME panel.
Writes use the revision loaded with the zone. A stale-revision error requires Refresh and reconciliation before retrying. If the response says changes were saved but a refresh is required, refresh the list instead of adding the record again. Save does not register domains, change registrar delegation or configure the target web/mail service.