Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Xloud DNS supports 12 standard DNS record types. Each type serves a specific purpose in DNS resolution. This reference covers the supported types, their value format, and usage examples for both Dashboard and CLI.
When creating records in the Dashboard, the form provides format hints and validation for each type automatically. See Manage Records for the step-by-step creation workflow.

Quick Reference

Record TypeFull NamePurpose
AAddress RecordMaps hostname to IPv4 address
AAAAIPv6 Address RecordMaps hostname to IPv6 address
CAACertificate Authority Authorization RecordControls which CAs can issue certificates
CNAMECanonical Name RecordHostname alias pointing to another name
MXMail Exchange RecordRoutes email to mail servers
NSName ServerDelegates a subdomain to other nameservers
PTRPointer RecordReverse DNS — maps IP to hostname
SOAStart Of AuthorityZone authority metadata (auto-managed)
SPFSender Policy FrameworkEmail sender validation policy
SRVService LocatorService discovery with host, port, priority
SSHFPSSH Public Key FingerprintPublishes SSH host key fingerprints
TXTText RecordArbitrary text data

Record Type Details

A — Address Record

Maps a hostname to one or more IPv4 addresses. The most common record type.
FieldValue
FormatIPv4 address
Example192.168.1.1
ValidationMust be a valid IPv4 address
Multiple valuesSupported — creates round-robin distribution
Select type A, enter the FQDN (e.g., www.example.com.), and add one or more IPv4 addresses in the Records field.
Multiple A records for the same name create DNS round-robin distribution — each resolver query cycles through the values. This is not a replacement for a proper load balancer but useful for simple traffic spreading.
Maps a hostname to an IPv6 address. Identical to A records but uses IPv6 notation.
FieldValue
FormatFull or abbreviated IPv6 address
Example2001:db8:3333:4444:5555:6666:7777:8888
ValidationMust be a valid IPv6 address
Select type AAAA and enter one or more IPv6 addresses in the Records field.
Restricts which Certificate Authorities can issue TLS certificates for the domain. Supported by major CAs to prevent unauthorized certificate issuance.
FieldValue
Format<flags> <tag> "<value>"
Example0 iodef mailto:security@example.com
Flags: 0 = non-critical (CA may issue even if tag is unknown), 128 = critical (CA must not issue if tag is unknown)Tags:
TagPurpose
issueAuthorizes a CA to issue certificates for this domain
issuewildAuthorizes a CA to issue wildcard certificates
iodefReporting URI for policy violations (e.g., mailto:security@example.com)
Select type CAA and enter the flag, tag, and value in the Records field (e.g., 0 issue "letsencrypt.org").
Creates an alias that points one hostname to another. The target must resolve to an A or AAAA record.
FieldValue
FormatFully qualified domain name
Exampleother-example.com
Name examplefirst.example.com.
CNAME records cannot coexist with other record types at the same name, and cannot be created at the zone apex (@). Use an A record for the root domain hostname.
Select type CNAME and enter the target FQDN in the Records field.
Specifies the mail servers responsible for receiving email for the domain. Multiple MX records with different priorities enable failover.
FieldValue
Format<priority> <hostname>
Example10 mail.example.com
Lower priority numbers have higher precedence. If the primary fails, resolvers try the next lowest priority.
Select type MX and enter each record as priority hostname. (e.g., 10 mail.example.com.).
Delegates a subdomain to a different set of nameservers. Zone apex NS records are auto-managed — do not modify them manually.
FieldValue
FormatNameserver FQDN
Examplens1.example.com
Select type NS and enter nameserver FQDNs in the Records field.
Maps an IP address back to a hostname. PTR records live in reverse zones (in-addr.arpa. for IPv4, ip6.arpa. for IPv6).
FieldValue
FormatReverse FQDN
Example1.1.0.192.in-addr.arpa.
For floating IP reverse DNS, use the dedicated Reverse DNS interface at Network > DNS Reverse instead of creating PTR records manually. See Reverse DNS.
Defines zone authority parameters. SOA records are auto-managed by the DNS service — you typically do not create or modify them directly.
FieldValue
Format<primary-ns> <admin-email> <serial> <refresh> <retry> <expire> <minimum>
Examplens1.example.com admin.example.com 2013022001 86400 7200 604800 300
ComponentDescription
Primary NSPrimary nameserver for the zone
Admin emailContact email (with . instead of @)
SerialVersion number, incremented on each change
RefreshSeconds between slave refresh checks
RetrySeconds between retry after failed refresh
ExpireSeconds before slave stops serving stale data
MinimumNegative caching TTL
Defines which mail servers are authorized to send email for the domain. Helps prevent email spoofing.
FieldValue
FormatSPF policy string
Example"v=spf1 ipv4=192.1.1.1 include:examplesender.email ~all"
Select type SPF and enter the SPF policy string in the Records field.
Modern practice is to publish SPF data as a TXT record rather than the dedicated SPF type. Most mail systems check TXT records for SPF. Consider creating both for maximum compatibility.
Specifies the host and port for a specific service. Used by SIP, XMPP, LDAP, and other service-discovery protocols.
FieldValue
Format<priority> <weight> <port> <target>.
Example10 0 5060 server1.example.com.
Name format_service._protocol.example.com. (e.g., _sip._tcp.example.com.)
ComponentDescription
PriorityLower = higher priority (like MX)
WeightLoad balancing between same-priority targets (higher = more traffic)
PortTCP/UDP port number for the service
TargetFQDN of the server hosting the service
Select type SRV. Enter the name as _service._protocol.domain. (e.g., _sip._tcp.example.com.) and the record as priority weight port target.
Publishes SSH host key fingerprints in DNS, allowing SSH clients to verify host keys via DNSSEC-secured lookups.
FieldValue
Format<algorithm> <fingerprint-type> <hex-fingerprint>
Example4 2 123456789abcdef67890123456789abcdef67890123456789abcdef123456789
AlgorithmKey Type
1RSA
2DSA
3ECDSA
4Ed25519
6Ed448
Fingerprint TypeHash
1SHA-1
2SHA-256
Select type SSHFP and enter the algorithm, fingerprint type, and hex fingerprint in the Records field.
Stores arbitrary text data. Widely used for domain ownership verification, SPF policies, DKIM keys, and DMARC.
FieldValue
FormatAny text string
Dashboard hint(no format hint shown — enter any text value)
Select type TXT and enter the text value in the Records field.

Next Steps

Manage Records

Create, update, and delete record sets using the Dashboard and CLI

Reverse DNS

Configure PTR records for your zone’s IP addresses

Create a Zone

Provision a new authoritative DNS zone

Troubleshooting

Resolve record conflicts and propagation issues