New resource records are created on the Resource Records tab of a zone. Address Manager supports the following types of resource records.
| Resource Record Type | Description |
|---|---|
| Host (A/AAAA) Record | Designates an IP address for a device. A new host requires a name and an IP address. Multiple addresses may exist for the same device. |
| Mail Exchanger Record | Designates the host name and preference for a mail server or exchanger. An MX record requires a name and a priority value. Priorities with a lower numeric value are chosen first in assessing delivery options. |
| CNAME Alias Record | Specifies an alias for a host name. The alias record type requires a name. |
| Service Record | Defines services available within a zone, such as LDAP. A service record requires a name, priority, port, and weight. A lower priority value indicates precedence. The port value indicates the port on which the service is available. The weight value is used when multiple services have the same priority value; a higher weight value indicates precedence. |
| HINFO Host Info Record | Specifies optional text information about a host. The host info record includes CPU and OS information. |
| TXT Text Record | Associates arbitrary text with a host name. A text record includes name and text information. This record is used to support record types such as those used in Sender Policy Framework (SPF) e-mail validation. |
| Naming Authority Pointer | Specifies a rewrite rule that when applied to an existing string will produce a new domain label or Uniform Resource Identifier (URI). This allows the DNS to be used to lookup services for a wide variety of resource names that are not in domain name syntax. NAPTR records are commonly used for Voice over Internet Protocol (VoIP), for example, in the mapping of servers and user addresses in the Session Initiation Protocol (SIP). |
| Generic Record | Allows generic configuration of the following resource
record types: A, AAAA, A6,
AFSDB, APL, CAA, CERT, DHCID,
DNAME, DS, IPSECKEY, ISDN, KEY,
KX, LOC, MB, MG, MINFO, MR, NS,
NSAP, PTR, PX, RP, RT, SINK,
SPF, SSHFP, TLSA, WKS, and X25. Note: The primary method for
creating A/AAAA records in Address Manager is by adding a host
record and linking it to an IP address.
Note: The A6 record type has
been moved to Historic status per RFC 6563, and is
planned for removal in a future release.
Note: The primary method for
creating PTR records is by selecting the Reverse
record checkbox during host record creation and
configuring necessary deployment roles. PTR records for
unmanaged external hosts can also be created as part of the IP
assignment process.
|
| HTTPS Record | A specialized version of the SVCB record designed for use
with HTTP. Allows for the aliasing of a full domain at the
zone apex (AliasMode). Also used to
configure multiple endpoints and provide clients with
connection information such as supported protocols, IP
addresses, and ports (ServiceMode). HTTPS
records are functionally the same as SVCB records but do not
require the encoding of the service name in the domain
name. |
| SVCB Record | Allows for the aliasing of a full domain at the zone apex
(AliasMode). Also used to configure
multiple endpoints and provide clients with connection
information such as supported protocols, IP addresses, and
ports, (ServiceMode). SVCB records share
the same functionality as HTTPS records but are generalized
and follow a naming convention where the service name is
encoded in the domain name. |
| URI Record | Maps a hostname to a URI. URI records share a similar functionality to SRV records, but return a full URI instead of a hostname and port number. URI records can also be seen as complementary to NAPTR records by allowing a querying party who already knows the service type to target a more specific subset of records. |