Skip to Content
Browse documentation

Common UAPP DNS Record Fields and Examples

Fill A, AAAA, CNAME, MX, TXT, NS, SRV and CAA record fields in UAPP DNS Manager with examples, numeric ranges and safe naming rules.

Use DNS Zones → Manage DNS → Add Record. The examples below assume the zone example.com and TTL 3600. Example domains and IP addresses illustrate field formats; replace them with values supplied for your actual service. Follow Add DNS Records for the complete save and verification workflow.

A — IPv4 address

FieldExample
TypeA
Name@
IPv4 Address192.0.2.10
TTL3600

This associates the apex name with an IPv4 address. Use www for www.example.com instead. Do not enter a URL, IPv6 address, hostname, port or network prefix. Adding an A record does not create the website on that server. Multiple A values at one name must share a TTL.

AAAA — IPv6 address

FieldExample
TypeAAAA
Namewww
IPv6 Address2001:db8::10
TTL3600

Enter one valid IPv6 address without a scope suffix such as %eth0, URL brackets or prefix length. Publish the real address only when the service is reachable there. An A record and AAAA record can coexist at the same name.

CNAME — alias target

FieldExample
TypeCNAME
Namewww
Alias Targetsite.example.net
TTL3600

Use a full target hostname; a trailing dot is optional in this form. Do not enter https://, a path or an address. The backend requires CNAME to be the only record at that owner, with one target. It cannot coexist with A, AAAA, TXT or other data there, and cannot replace the apex's required SOA/NS records. CNAME does not implement HTTP redirection.

MX — mail server

FieldExample
TypeMX
Name@
Mail Servermail.example.net
Priority10
TTL3600

Mail Server is a hostname, not an IP address or mailbox. Put the numeric priority in Priority, not at the start of Mail Server. Priority must be 0–65535. Lower values are preferred by mail senders; multiple MX records use the provider's supplied priorities. See RFC 1035.

Use the mail provider's exact targets. An MX record alone does not create mailboxes or change Eenos local/remote mail exchange routing; configure Email routing as required. Do not remove existing mail records without understanding the migration.

TXT — text or verification value

FieldExample
TypeTXT
Name_verify
Text Valueprovider-verification=replace-with-issued-token
TTL3600

Paste the logical value into the multiline Text Value field without surrounding zone-file quotes. The backend handles escaping and splitting long TXT data into DNS character strings; do not paste an entire zone-file record. The form requires content.

Typical owner names include @ for an apex policy, _dmarc for a DMARC policy, and a provider-supplied selector._domainkey for DKIM. Use the actual public value from the service; never publish a private signing key. Existing policy controls may already generate needed records. The validator rejects duplicate SPF policies at one owner and duplicate DMARC policies at _dmarc; combine or revise the intended policy rather than adding a second one blindly.

NS — nameserver

FieldExample
TypeNS
Name@
Nameserverns1.example.net
TTL3600

Enter a full nameserver hostname. @ publishes apex NS data; a relative name such as department represents that owner within this zone. Preserve the required apex nameserver set. Adding NS data here does not update registrar delegation or required nameserver glue. Coordinate those separately with the provider.

SRV — service location

FieldExample
TypeSRV
Name_sip._tcp
Service Targetsip.example.net
Priority10
Weight5
Port5060
TTL3600

Priority, Weight and Port are separate required integers, each 0–65535. The target is a hostname; do not include the port there. Use the exact service/protocol owner and values required by the application. Lower priority is preferred; weight helps selection among targets with equal priority. The record does not start a service or open its firewall port. See RFC 2782.

CAA — certificate policy

FieldExample
TypeCAA
Name@
Policy Valueca.example.net
Flags0
Tagissue
TTL3600

Flags is 0–255; Tag must be 1–15 alphanumeric characters. Policy Value is logical text without manually adding zone-file quotes. The illustrated CA hostname is a placeholder, not an issuance recommendation. Use the actual authority's policy requirements and review wildcard/other relevant authorizations before saving. An incorrect CAA policy can prevent certificate issuance; syntactic acceptance does not prove the CA recognizes the value.

All numeric options must be integers. Server validation can be stricter than the browser's generic input maximum. After saving, inspect the result and authoritative DNS answers; existing caches can retain prior data for their remaining TTL.