A record
An Address record maps a domain name to a 32-bit IPv4 address. It is one of the most common DNS data types and is normally used for forward name resolution.
Category glossary
Search all termsResource record
34 definitions associated with Resource record.
AAAA record
An IPv6 Address record maps a domain name to a 128-bit IPv6 address. The name is pronounced "quad A".
CAA record
A Certification Authority Authorization record states which certificate authorities are permitted to issue certificates for a domain and can define incident-reporting contacts. Certificate authorities are expected to check it before issuance.
CDNSKEY record
A Child DNSKEY record published by a child to request that the parent create or update a corresponding DS record. It is an alternative signal to CDS for automated delegation maintenance.
CDS record
A Child DS record published in a child zone to signal desired DS changes to the parent. It supports automated DNSSEC delegation maintenance when the parent follows a defined acceptance policy.
Certificate association (TLSA)
A TLSA record binds a TLS service endpoint to an expected certificate or public key. It is the core DNS record used by DANE and is meaningful when protected by DNSSEC.
CNAME record
A Canonical Name record makes its owner name an alias for a target name. With limited DNSSEC-related exceptions, other data should not coexist at the same owner name.
CSYNC record
A Child-to-Parent Synchronization record allows a child zone to signal selected delegation-data changes, such as NS and related address records, to its parent under an agreed automation policy.
Delegation signer (DS) record
A record in a parent zone that authenticates a DNSKEY in the child zone. It forms the secure link between parent and child in the DNSSEC chain of trust.
DHCID record
A DNS record that stores a digest representing a DHCP client identity and name association. It helps DHCP servers detect ownership conflicts during coordinated dynamic DNS updates.
DNAME record
A Delegation Name record redirects an entire subtree of names to another subtree, unlike CNAME which aliases a single owner name. Resolvers synthesize a CNAME-like result for the queried descendant.
DNSKEY record
A record containing a public key used to verify DNSSEC signatures made by the corresponding private key. DNSKEYs commonly serve as zone-signing or key-signing keys based on operational role.
DS record
A Delegation Signer record in a parent zone contains a digest of a child DNSKEY and identifies the algorithm and digest type. It creates a signed delegation in the chain of trust.
DSYNC record
A DNS record used to publish the location of a service that synchronizes delegation-related data between child and parent. It supports automated delegation maintenance workflows.
HINFO record
A Host Information record that can describe CPU and operating system text for a host. It is rarely used on the public Internet because the information can become stale or reveal unnecessary detail.
HTTPS record
The HTTPS service binding record, a specialized SVCB form for HTTPS endpoints. It can advertise alternative endpoints, protocols, ports, encrypted-client-hello parameters, and address hints.
LOC record
A Location record encodes geographic coordinates, altitude, size, and precision for a domain name. It is not widely deployed and should not be relied on as a current asset-location system.
MX record
A Mail Exchange record identifies mail servers for a domain and assigns each a preference value. Lower preference values are tried first, with equal values treated as alternatives.
NAPTR record
A Naming Authority Pointer record applies ordered rewriting rules to discover services or transform identifiers. It is used in ENUM, SIP, and other naming systems, often together with SRV records.
NS record
A Name Server record identifies an authoritative server for a zone or delegated child. Apex authoritative NS records and parent-side delegation NS records are separate RRsets.
NSEC record
A DNSSEC record that links to the next existing name in canonical order and lists record types present at its owner. It proves name or type nonexistence but can permit zone walking.
NSEC3 record
A hashed denial-of-existence record designed to make straightforward zone enumeration more difficult than NSEC. It adds iterations, salt, and opt-out behavior, with operational and computational tradeoffs.
NSEC3PARAM record
A zone-apex record publishing the NSEC3 parameters used to generate hashed owner names, such as algorithm, iterations, and salt. Validators primarily rely on parameters in NSEC3 records themselves.
NXNAME record
A DNS record type assigned for compact denial of existence. It is intended to support efficient authenticated nonexistence mechanisms defined by its associated specification.
PTR record
A Pointer record maps a reverse-domain name to another domain name, most commonly mapping an IPv4 or IPv6 address to a host name. Multiple PTRs are technically possible but can confuse applications.
RESINFO record
The Resolver Information record lets a resolver publish information about its capabilities or configuration through key-value data. Clients can discover it using the resolver.arpa framework.
RRSIG record
A DNSSEC signature record covering an RRset. It identifies the covered type, algorithm, signer, key tag, inception and expiration times, and cryptographic signature.
SOA record
The Start of Authority record identifies key zone parameters including MNAME, RNAME, serial, refresh, retry, expire, and minimum fields. Every authoritative zone has an SOA at its apex.
SRV record
A Service record identifies the target host and port for a named service, with priority and weight values for selection. The owner name normally begins with _service._protocol.
SVCB record
A Service Binding record that describes alternative service endpoints and connection parameters. It supports alias mode and service mode and is the base format specialized by the HTTPS record.
TLSA record
A record that associates a TLS service with an expected certificate or public key using usage, selector, and matching fields. Secure use depends on DNSSEC validation.
TXT record
A Text record contains one or more character strings, each limited to 255 octets in wire format. TXT is used by many applications for verification, email policy, security, and metadata, with application-specific syntax.
Zone digest
A cryptographic digest over canonical zone data used to verify that a transferred or published zone is complete and unmodified. The ZONEMD record carries the digest at the zone apex.
ZONEMD record
A Message Digest Over Zone Data record that provides a digest of the zone contents. It can detect corruption or incomplete distribution but does not replace DNSSEC authentication of individual answers.