Supported DNS Record Types (DNS RR types)
What are DNS Record Types?
DNS record types define the kind of information stored in a DNS zone and how a domain behaves on the internet. Each record type serves a specific purpose, such as pointing a domain to an IP address, configuring email delivery, enabling security features, or defining service routing rules.
When a domain is queried, DNS resolvers use these record types to determine how to handle the request.
Supported Record Types
At OpusDNS we support the following DNS Record Types:
- A
- AAAA
- ALIAS
- CAA
- CNAME
- DNSKEY
- DS
- MX
- NS
- PTR
- TXT
- SOA
- SRV
- TLSA
- SMIMEA
- URI
- HTTPS
- SVCB
- NAPTR
- SSHFP
Usage Guide, Examples and Formats
Below you’ll find a short explanation and example format for each supported record type.
A Record
Maps a domain to an IPv4 address.
Example:
- Name:
example.com - Value:
192.0.2.1
AAAA Record
Maps a domain to an IPv6 address.
Example:
- Name:
example.com - Value:
2001:db8::1
ALIAS Record
Allows a domain to point to another hostname at the zone apex (similar to CNAME but for root domains).
Example:
- Name:
example.com - Value:
example.net
CAA Record
Specifies which certificate authorities are allowed to issue certificates for the domain.
Example:
- Name:
example.com - Value:
0 issue "letsencrypt.org"
CNAME Record
Maps a domain or subdomain to another hostname.
Example:
- Name:
www - Value:
example.com
DNSKEY Record
Holds the public key used in DNSSEC for verifying DNS data.
Example:
- Managed automatically or provided by DNSSEC configuration.
DS Record
Delegation Signer record used in DNSSEC to link parent and child zones.
Example:
- Name:
example.com - Value:
12345 8 2 abcdef...
MX Record
Defines mail servers responsible for receiving emails.
Example:
- Name:
example.com - Value:
10 mail.example.com
NS Record
Specifies authoritative nameservers for a domain.
Example:
- Name:
example.com - Value:
ns1.opusdns.com
PTR Record
Used for reverse DNS lookups (IP → domain).
Example:
- Name:
1.2.0.192.in-addr.arpa - Value:
example.com
TXT Record
Stores arbitrary text data, often used for verification or email security.
Examples:
- SPF:
v=spf1 include:_spf.example.com ~all - Verification:
google-site-verification=abc123
SOA Record
Start of Authority record containing zone metadata.
Example:
- Primary NS, admin email, serial number, refresh timers.
SRV Record
Defines service locations (host and port).
Example:
- Name:
_sip._tcp.example.com - Value:
10 60 5060 sipserver.example.com
TLSA Record
Used for DANE, linking TLS certificates to DNS.
Example:
- Name:
_443._tcp.example.com - Value:
3 1 1 abcdef...
SMIMEA Record
Used for binding S/MIME certificates to a domain.
Example:
- Name:
user._smimecert.example.com - Value: hash of certificate
URI Record
Maps a domain to a URI.
Example:
- Name:
_service.example.com - Value:
10 1 "https://example.com/service"
HTTPS Record
Defines HTTPS service parameters and endpoints.
Example:
- Name:
example.com - Value:
1 . alpn="h3,h2"
SVCB Record
Service Binding record used for advanced service configuration.
Example:
- Name:
example.com - Value:
1 example.com alpn="h2"
NAPTR Record
Used for dynamic service resolution (often in VoIP systems).
Example:
- Name:
example.com - Value:
100 10 "u" "E2U+sip" "!^.*$!sip:info@example.com!" .
SSHFP Record
Stores SSH public key fingerprints for server verification.
Example:
- Name:
example.com - Value:
1 1 <hash>