Skip to Content
Browse documentation

Advanced UAPP DNS Record Fields and Examples

Configure TLSA, PTR, AFSDB, DNAME, DS, HINFO, LOC, NAPTR, RP, SVCB and HTTPS fields with exact validator ranges and record-format examples.

Use Add DNS Records for the procedure. Every type below also requires Name and TTL. Examples assume example.com and TTL 3600; replace all illustrative names and values with data supplied for the service. Numeric fields require integers, and the DNS parser applies additional type-specific checks.

TLSA

Certificate Association Data is hexadecimal data without separators or a complete TLSA record. Additional fields are Usage 0–3, Selector 0–1 and Matching Type 0–2. Matching Type 1 requires 64 hexadecimal characters; type 2 requires 128. Type 0 carries the full association data rather than a hash of those lengths.

Format example: Name _443._tcp.www, Usage 3, Selector 1, Matching Type 1, with a 64-character SHA-256 association value in Certificate Association Data. Obtain that value from the actual certificate/key workflow. Do not publish an invented digest: correct syntax does not establish a correct association or complete DNSSEC/DANE deployment.

PTR

Pointer Target is a full hostname, such as host.example.net. A PTR used for reverse DNS belongs in the correctly delegated reverse zone. For an illustrative 2.0.192.in-addr.arpa zone, Name 10 and Pointer Target host.example.net produce 10.2.0.192.in-addr.arpa.

Adding a PTR named 10 in the ordinary example.com zone creates 10.example.com, not the reverse record for an IP address. Ask the address provider to publish or delegate reverse DNS where required; UAPP ownership of a forward domain is not reverse-zone authority.

AFSDB

Enter the full hostname in AFS Database Server and a required Subtype from 0–65535. Format example: Name @, server afsdb.example.net, Subtype 1. Use the subtype specified by the actual service rather than treating every accepted number as a usable configuration.

DNAME

Enter the full hostname in Alias Target. Format example: Name legacy, Alias Target archive.example.net. No additional fields appear. The zone validator permits only one DNAME target at an owner. DNAME and CNAME are different DNS mechanisms; do not use this field as a website redirect or assume it installs a replacement service.

DS

Enter hexadecimal Digest data and required Key Tag 0–65535, Algorithm 0–255 and Digest Type 0–255. Known digest lengths enforced by this backend are type 1: 40 hex characters, type 2: 64, and type 4: 96. The parser can reject unsupported combinations.

Format example: Name child, Key Tag 12345, Algorithm 8, Digest Type 2, with the actual 64-character digest issued for the child zone's key. Obtain every value from the DNSSEC operator. This example is a field layout, not a valid trust anchor. A domain's parent-side DS publication must be coordinated with its registrar/parent operator; creating DS in an unrelated forward zone does not complete DNSSEC delegation.

HINFO

Enter plain CPU Description and required Operating System text. Format example: Name host, CPU Description X86_64, Operating System Linux. Do not manually combine or quote these as a zone-file RDATA fragment; the encoder handles the two strings. Publish this descriptive system information only when intended.

LOC

Enter the full location expression in Location Coordinates. Format example: Name office, coordinates 37 47 0 N 122 24 0 W 10m. No additional fields appear. The DNS parser validates the coordinate syntax; newline, semicolon and parenthesized fragments are rejected. Do not use LOC as a generic postal-address field, and review the privacy implications of publishing a precise location.

NAPTR

Enter Replacement Target, required Order and Preference (both 0–65535), and the text fields Flags, Service and Regular Expression. Those three text inputs may be blank in this form. Flags is text for NAPTR, unlike CAA's numeric Flags.

Format example: Name @, Replacement Target _sip._udp.example.net, Order 100, Preference 10, Flags s, Service SIP+D2U, and an empty Regular Expression. Supply separate fields without zone-file surrounding quotes. Use the service's actual discovery/rewriting specification; accepted syntax alone does not establish working client discovery. A . replacement is meaningful only when appropriate to the supplied expression/service.

RP

Responsible Mailbox accepts an email address such as hostmaster@example.com, or . for none. The backend converts an email address to DNS mailbox representation; do not manually replace every dot in the mailbox with an @.

TXT Domain is required and is a full hostname pointing to descriptive TXT data, or . where no TXT domain is intended. Format example: Name @, Responsible Mailbox hostmaster@example.com, TXT Domain contact.example.com. The target's TXT record is a separate record; RP does not create it or a mailbox.

SVCB and HTTPS

Both use Service Target, required Priority 0–65535 and optional Service Parameters. Parameters are a single line of supported DNS service-parameter syntax, such as alpn="h2,h3" port=443; do not paste the full priority/target/RDATA into that field.

ModeField exampleValidation
AliasType HTTPS, Name @, Service Target svc.example.net, Priority 0, Service Parameters blankRequires a non-. target and no parameters.
ServiceType HTTPS, Name @, Service Target ., Priority 1, Service Parameters alpn="h2,h3" port=443Positive priority; . represents this service's owner name.

For SVCB, use the owner and parameters required by the relevant service. The backend DNS parser validates and canonicalizes parameters. Publishing an HTTPS record does not enable HTTP/3, create a TLS certificate or configure the server. Service and client capabilities must actually match. See RFC 9460.

Validation and verification

The browser's generic numeric inputs can offer a larger maximum than the individual record type supports. Use the ranges above and read the server's error. Every owner must remain relative to the selected zone, while hostname targets are full names with an optional final dot in this panel. SOA is unavailable in UAPP.

Save one intended change, inspect the resulting row and options, and verify authoritative answers and service behavior. A valid record can still point to the wrong service or use an incorrect provider-issued digest, policy or parameter. Preserve working values before replacement.