Skip to main content

Overview

Polystack 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 Type Details

A — Address Record

Maps a hostname to one or more IPv4 addresses. The most common record type.
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.
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.Flags: 0 = non-critical (CA may issue even if tag is unknown), 128 = critical (CA must not issue if tag is unknown)Tags:
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.
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.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.
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).
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.
Defines which mail servers are authorized to send email for the domain. Helps prevent email spoofing.
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.
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.
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.
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