Supported Resource Records
The Oracle Cloud Infrastructure DNS service supports many resource record types. The following list provides a brief explanation of the purpose of each supported record type for public DNS. For private DNS, see Private DNS Supported Resource Records. Avoid entering confidential information when entering record data. The RFC links direct you to further information about the record types and data structure.
Note About RDATA
Oracle Cloud Infrastructure normalizes all RDATA into the most machine readable format. The returned presentation of your RDATA may differ from its initial input.
The RDATA for the ALIAS, CNAME, DNAME, MX, and NS record types may contain one or more absolute domain names. If the specified RDATA for one of these record types does not end in a dot or period to represent the root, the period will be added.
www.example.com --> www.example.com.
You can use various DNS libraries to normalize your RDATA before input.
Public DNS Resource Record Types
- An address record used to point a hostname to an IPv4 address. For more information about A records, see RFC 1035.
- An address record used point a hostname at an IPv6 address. For more information about AAAA records, see RFC 3596.
- A non-standard DNS record type that allows CNAME functionality at the apex of a zone. ALIAS records cannot co-exist with steering policy attachments on a domain.
- A Certification Authority Authorization record allows a domain name holder to specify one or more Certification Authorities authorized to issue certificates for that domain. For more information about CAA records, see RFC 6844.
- A Certificate record stores public key certificates and related certificate revocation lists in the DNS. For more information about CERT records, see RFC 2538 and RFC 4398.
- A Canonical Name record identifies the canonical name for a domain. For more information about CNAME records, see RFC 1035.
- A Child-to-Parent Synchronization record syncs records from a child zone to a parent zone. For more information about CNAME records, see RFC 7477.
- A DHCP identifier record provides a way to store DHCP client identifiers in the DNS to eliminate potential hostname conflicts within a zone. For more information about DHCID, see RFC 4701.
- A Delegation Name record has similar behavior to a CNAME record, but allows you to map an entire subtree beneath a label to another domain. For more information about DNAME records, see RFC 6672.
A Delegation Signer record resides at the top-level domain and points to a child zone's DNSKEY record. DS records are created when DNSSEC security authentication is added to the zone. For more information about DS records, see RFC 4034.
- An IPSec Key record stores public keys for a host, network, or application to connect to IP security (IPSec) systems. For more information on IPSECKEY records, see RFC 4025.
- A Key record stores a public key that is associated with a domain name. Currently only used by SIG and TKEY records. IPSECKEY and DNSKEY have replaced key for use in IPSec and DNSSEC, respectively. For more information about KEY records, see RFC 4025.
- A Key Exchanger record identifies a key management agent for the associated domain name with some cryptographic systems (not including DNSSEC). For more information about KX records, see RFC 2230.
- A Location record stores geographic location data of computers, subnets, and networks within the DNS. For more information about LOC records, see RFC 1876.
- A Mail Exchanger record defines the mail server accepting mail for a domain. MX records must point to a hostname. MX records must not point to a CNAME or IP address. For more information about MX records, see RFC 1035.
- A Naming Authority Pointer record stores information used by ENUM (Telephone Number Mapping) to map E.164 numbers to URIs. For more information about NAPTR records, see RFC 3403.
- A Nameserver record lists the authoritative nameservers for a zone. Oracle Cloud Infrastructure DNS automatically generates NS records at the apex of each new primary zone. For more information about NS records, see RFC 1035.
- A Network Service Access Point record maps a domain name to an NSAP address. For more information about NSAP records, see RFC 1637.
- A Pointer record reverse maps an IP address to a hostname. This behavior is the opposite of an A Record, which forward maps a hostname to an IP address. PTR records are commonly found in reverse DNS zones. For more information about PTR records, see RFC 1035.
- A resource record used in X.400 mapping protocols. For more information about PX records, see RFC 822 and RFC 2163.
- A Responsible Person record contains information on how to contact the designated responsible parties for a domain. For more information about RP records, see RFC 1183.
A Start of Authority record specifies authoritative information about a DNS zone, including:
- The primary nameserver.
- The email of the domain administrator.
- The domain serial number.
- Several timers relating to refreshing the zone.
The Oracle Cloud Infrastructure DNS automatically generates an SOA record when a zone is created. For more information about SOA records, see RFC 1035.
- A Sender Policy Framework record is a special TXT record used to store data designed to detect email spoofing. For more information about SPF records, see RFC 4408.
- A Service Locator record allows administrators to use several servers for a single domain. For more information about SRV records, see RFC 2782.
- An SSH Public Key Fingerprint record publishes SSH public host key fingerprints using the DNS. For more information about SSHFP records, see RFC 6594.
- A Transport Layer Security Authentication record associates a TLS server certificate, or public key, with the domain name where the record is found. This relationship is called a TLSA certificate association. For more information about TLSA records, see RFC 6698.
- A Text record holds descriptive, human readable text, and can also include non-human readable content for specific uses. It is commonly used for SPF records and DKIM records that require non-human readable text items. For more information about TXT records, see RFC 1035.