Resource Records of DNS Types and Uses

DNS records come in many types, each serving a specific purpose in the online world.

A SOA record is used to identify the authoritative name server for a domain, specifying the name of the server, its email address, and other details.

The NS record tells the world which name servers are responsible for a domain, ensuring that users can find the correct information.

MX records are used by email providers to specify the mail servers that handle incoming emails for a domain, directing messages to the right place.

You might enjoy: Email Dns Records

Understanding DNS is crucial to grasping how resource records work. Resource records are the building blocks of the Domain Name System (DNS), and they're made up of a hierarchical structure of name, TTL, type, and data.

A resource record's name is the domain name to which it pertains, and it must always start in column 1. If the name field is left blank, the record takes the name of the previous resource record.

The TTL, or time to live, specifies how long the resource record is stored by the LDNS, but it's optional. If this field is left blank, the default TTL value is specified in the start of authority (SOA) resource record.

The address class is the third field, and currently, only one class is supported: IN, for internet addresses and other internet information. Limited support is included for the HS class, which is for MIT/Athena "Hesiod" information.

Resource Records (RRs) are the fundamental information elements of the Domain Name System (DNS). Each RR defines a specific piece of information about the domain.

The combination of these elements within a DNS record allows DNS servers to accurately resolve queries by clients for various services related to a domain. Here are some common types of DNS records:

DNS Record Types are used to store and retrieve information in the DNS database. They are the building blocks of the DNS system, and understanding them is crucial for anyone working with DNS.

There are many types of DNS Record Types, including A, CNAME, MX, NS, PTR, and SOA records. These are the most common types of records, and they are used for different purposes such as mapping host names to IP addresses, defining host aliases, and identifying name servers for a domain.

Here are some of the most common DNS Record Types:

In addition to these common types, there are also less common types of DNS Record Types, such as AAAA, AFSDB, GPOS, HINFO, and ISDN records.

On a similar theme: List of DNS Record Types

Alias records are only available for Cloud DNS public zones. They're not compatible with private zones, so if you're working with a private zone, you won't be able to use ALIAS records.

For CNAME records, the resolver is responsible for resolving the canonical name. But with ALIAS records, the Cloud DNS name server takes over and resolves the canonical name, producing synthesized A or AAAA records to return to the resolver.

The synthesized A or AAAA records have the ALIAS record's name with the IP addresses found from resolving the ALIAS record's target. This is how Cloud DNS handles ALIAS records, by producing new records on the fly.

Cloud DNS returns all of the records if the alias target resolves to a resource record set (RRSet) with multiple addresses. But it randomizes their order before returning the synthesized address record, which is a nice touch.

Only address records are synthesized during ALIAS record target resolution. No other types of records are produced in this process.

If the ALIAS target resolution fails, the Cloud DNS name server returns a SERVFAIL response to its client. This is a serious error message that indicates something went wrong.

Cloud DNS doesn't use client-provided EDNS Client Subnet when resolving ALIAS record targets. This means the client's IP address won't be taken into account during the resolution process.

Related reading: Dns Resolution Error

The Time to Live (TTL) value is a crucial parameter in DNS records, determining how long a record is stored by the LDNS.

TTL is optional, but if left blank, the default TTL value is specified in the start of authority (SOA) resource record.

A TTL value is used to control caching, which can significantly impact DNS resolution times.

The TTL value returned with a synthesized address record is the smallest of the ALIAS record's configured TTL value and the TTL values that are encountered while resolving the ALIAS target.

In a Cloud DNS managed zone, a query for the A record at example.com returns a response with a TTL value of 3000, which is the smallest of the TTLs encountered during resolution (6000 for the ALIAS record, 3000 for the CNAME record, and 5000 for the A record).

This means that the TTL value can be less than the ALIAS record's configured TTL, but it's never greater than the configured TTL.

Here's a summary of how TTL is determined for synthesized address records:

This example illustrates how TTL values are combined to determine the final TTL for a synthesized address record.

The Address record, or A record, is a crucial part of DNS record types. It lists the IP address for a given host name.

The name field in an A record is the host's name, and the address is the network interface address. There should be one A record for each IP address of the machine.

Figure C.1 shows an example of an A record, which includes the host name, TTL, addr-class, type, and address. For instance, the A record for host1.siterequest.com has two IP addresses: 128.32.0.4 and 10.0.0.78.

A record TTLs can be influenced by the TTLs of other records encountered during resolution. This can result in a TTL returned in the synthesized address record that's less than the A record's configured TTL.

Here are the six most common types of resource records, including the A record:

Cname (Canonical Name) records are used to specify an alias or nickname for the official host name. This record must be the only one associated with the alias name.

A CNAME record is usually created when you have one A record for a given address and want to define alias host names for that address. This makes it easier to manage multiple host names that point to the same IP address.

Here's an example of a CNAME record: alias {ttl} addr-class {type} Canonical name wip.siterequest.com IN CNAME host1.siterequest.com. This example shows that wip.siterequest.com is an alias for host1.siterequest.com.

In a CNAME record, the Canonical name field specifies the official host name that the alias points to. In our example, the Canonical name is host1.siterequest.com.

Here's an interesting read: Dns Records Example

The SOA (Start of Authority) record is a crucial part of DNS record types, and it's used to indicate that a name server is the best source of information for a particular zone.

Every zone needs exactly one SOA record, and it's usually the first record in the zone file. The SOA record is used to define the default parameters for a zone, including the person in charge of the name server, the serial number of the data file, and the time intervals for refresh, retry, expire, and minimum TTL.

Discover more: SOA Record

The SOA record also includes the email address for the person responsible for the name server, which is used when the SOA record is updated. This email address is created by replacing the at character (@) with a dot (.). For example, if the email address is [email protected], it would be written as johndoe.berkeley.edu in the SOA record.

The serial number in the SOA record is a positive integer that must be increased whenever a change is made to the data file. This helps ensure that secondary name servers are aware of the latest changes and can update their data accordingly.

The refresh time interval, which is specified in seconds, determines how often secondary name servers check with the primary name server to see if an update is necessary. If a secondary server fails to receive an update, it will wait for the retry time interval before trying again.

The expire time interval sets the maximum number of seconds that a secondary name server can use the data before it expires for lack of receiving a refresh. This helps prevent stale data from being used.

The minimum TTL field in the SOA record sets the default time to live for resource records that don't specify a TTL. It also enforces a minimum TTL if one is specified on a resource record in the zone.

Related reading: Cloudfare Dns Server

Here's a breakdown of the specific fields in an SOA record:

Wildcard records are supported by Cloud DNS, but there's a catch: they can't be used for NS records.

You can use wildcard records for all other record types, which makes them super versatile.

Cloud DNS supports wildcard records for all record types, except for NS records.

Wildcard records are a great way to simplify your DNS setup, especially if you have a large number of subdomains.

For example, you can use a wildcard record to route all subdomains to a single IP address.

Wildcard records can be a real time-saver, and they're a key feature of Cloud DNS.

Just remember, wildcard records aren't allowed for NS records, so be sure to keep that in mind when setting them up.

Worth a look: Wildcard DNS Record

RR Types are used in DNS to define the type of record being queried or transferred. There are several types of RR Types, including pseudo-RRs, which are not part of the standard DNS protocol.

Curious to learn more? Check out: Dns Query Types

The "type" field in the DNS protocol is also used for various operations, including the ANY query, which returns all records of all types known to the name server. The ANY query can return incomplete records, as seen in the example of a name server having only an A record cached for a name that also has an MX record.

The standard resource record format, as specified in RFC 1035, includes a "type" field that defines the type of the record. The type field can be any of the RR Types, such as A, NS, or CNAME.

Some RR Types are used for specific purposes, such as the OPT record, which is a pseudo-record type needed to support EDNS. Other RR Types, like the ALIAS record, are used for aliasing similar to DNAME records.

The most common RR Types are A, CNAME, MX, NS, PTR, and SOA. These are the most frequently used RR Types in DNS.

Here are the most common RR Types:

The RR Types can be divided into several categories, including data TYPEs, Q TYPEs, Meta TYPEs, data RRTYPEs, and private use. The registration procedures for RR Types vary depending on the category, with some requiring expert review or standards action.

There are different types of synchronization endpoints, each with its own purpose. The location of these endpoints is determined by the RRtype and scheme used.

The null scheme, with a value of 0, is a no-op and does not perform any synchronization. This is useful for testing or debugging purposes.

The CDS and CSYNC RRtypes both use the NOTIFY scheme, with a value of 1, for delegation management. This allows for the synchronization of delegation information.

RRtypes with values between 2 and 127 are currently unassigned. This means that they are not yet defined or reserved for future use.

RRtypes with values between 128 and 255 are reserved for private use. This means that they can be used by organizations or individuals for their own purposes, but should not be used in public DNS systems.

Here is a summary of the synchronization locations:

DNS resource records are not limited to A, NS, and CNAME records. There are several other types of records that serve different purposes.

The "*" record type, also known as ANY, returns all records of all types known to the name server. This record type is used to retrieve all cached records for a given name.

The "AXFR" record type is used for Authoritative Zone Transfer, which transfers an entire zone file from the primary name server to secondary name servers. This record type is used to synchronize DNS data between name servers.

Other DNS Record Types

These record types are used for various purposes, including providing host information, geographical position, and IPv6 addresses. They are an essential part of the DNS system, enabling efficient and accurate data retrieval.

An ALIAS record is a Cloud DNS custom record type that behaves like a CNAME record but can only be used at the zone apex and only responds to address record (A or AAAA) queries.

ALIAS records map an alias domain name to a canonical name and use the canonical name to look up the answer. This record type is useful when you need CNAME behavior at the apex, but you cannot place a CNAME record at the apex because it cannot exist alongside any other record type, including the SOA record that is required at the zone apex.

On a similar theme: Cname Records in Dns

Cloud DNS manages ALIAS records like all other records, and you can view the details of an ALIAS record in the Cloud DNS console.

The ALIAS record type is specific to Cloud DNS and is never exposed to an external client querying Cloud DNS zones. For a client, an ALIAS record appears as a standard A or AAAA record in the DNS response.

You can enable logging for ALIAS records to record information about the status of the ALIAS name resolution. The alias_query_response_code is only set if the query is resolved using an ALIAS record, and a value of NoError means that the ALIAS record was resolved successfully.

Here are some key facts about ALIAS records:

ALIAS records can be managed like all other records, and you can view the details of an ALIAS record in the Cloud DNS console.

Underscored and Globally Scoped Node Names are used to identify specific types of DNS records. These node names are used in conjunction with various RR types to provide additional information about a domain.

One of the most common underscored node names is _example, which is used with the * RR type. This is defined in RFC8552, Section 4.1.4.

Some other examples of underscored node names include _signal, which is used with the CDNSKEY and CDS RR types, and _dsync, which is used with the DSYNC RR type. These node names are used to provide additional information about a domain's DNS records.

Here are some examples of underscored node names and the RR types they are used with:

These underscored node names provide a way to identify specific types of DNS records and provide additional information about a domain.

In a DNS database file, resource records can have additional fields depending on their type. These fields are specific to the type of record.

The standard resource record format is specified in RFC 1035, which includes a name, TTL, address class, record type, and record-specific data. The fields in a resource record are defined as follows:

Comparisons and lookups in the name server database are not case-sensitive, even though case is preserved in names and data fields when loaded into the name server.

Expand your knowledge: Fortigate Dns Server

Zone Version Types are a crucial aspect of DNS records. There are specific ranges of values for the ZONEVERSION TYPE field.

The ZONEVERSION TYPE field has a range of 0-255. Here's a breakdown of what each range means:

Each value in the ZONEVERSION TYPE field has a specific meaning. For example, a value of 0 is referred to as SOA-SERIAL.

The "ANY" pseudo-record type is a special case that returns all records of all types known to the name server. This can be useful for debugging purposes, but be aware that the records returned may not be complete.

RFC 1035 defines the "ANY" pseudo-record type with a type ID of 255. However, in 2019, RFC 8482 led many DNS providers to provide only minimal responses to "ANY" queries, instead of enumerating records.

The "OPT" pseudo-record type is another special case, with a type ID of 41, defined in RFC 6891. It's used to support EDNS.

Here are some pseudo-record types that serve as alternatives to CNAMEs, including ALIAS, ANAME, apex CNAME, and top-level redirection. These types are not RFC-standardized and their implementation varies, but they're commonly used to cause the DNS software vendor to synthetically generate A and AAAA records similar to the ones of the ANAME-records destination.

Obsolete record types are still used in some legacy systems, but they're no longer recommended for new developments.

The IBM System/360, introduced in 1964, used a 4-byte record type called the "fullword" record.

Using obsolete record types can lead to compatibility issues and make maintenance more difficult.

The IEEE 754 floating-point standard, which was introduced in 1985, uses a 32-bit and 64-bit record type for floating-point numbers.

These record types are still widely used in many programming languages and libraries, including C, C++, and Fortran.

The use of obsolete record types can also lead to security vulnerabilities, as they may not be as secure as newer record types.

The C standard library, for example, uses the 32-bit and 64-bit record types for floating-point numbers.

Dhcid Rr Digest Codes are a type of pseudo-RR, which is not a valid RR type. Dhcid Rr Digest Codes are used to store information about the status of a request.

They are stored in the RR's rdata field, which is a binary field that can contain various types of data. The format of Dhcid Rr Digest Codes is specific and follows a defined structure.

Dhcid Rr Digest Codes are not used to store any meaningful information about the request. They are simply used to store a digest of the RR's rdata field.

The use of Dhcid Rr Digest Codes is not recommended as they can cause issues with the RR's processing.

When importing records, you can choose between a BIND zone file or a YAML file. Importing from a BIND file is a great option if you're working with existing DNS software.

ALIAS records are not supported in BIND files, so keep that in mind if you're planning to import records that include ALIAS entries. They will be exported to YAML files, specifically in the Cloud DNS format.

Importing a zone file in BIND format is a quick way to create all the records for your zone, thanks to DDI Central.

DDI Central and Monitoring is a crucial part of managing DNS resource records. It's a centralized system that allows administrators to monitor and manage DNS data in real-time.

DDI Central and Monitoring can be integrated with various DNS services, including DNSSEC, which ensures the authenticity and integrity of DNS data. This integration is especially useful for organizations with a large number of DNS servers.

By using DDI Central and Monitoring, administrators can quickly identify and troubleshoot DNS-related issues, reducing downtime and improving overall network performance.

If this caught your attention, see: Charging Data Record

Creating in DDI Central is a straightforward process. You can add or update resource records for a particular domain by clicking on the domain name from the list of domains you intend to create or update DNS records.

To create a new record, select the relevant record type, such as A, AAAA, or ANAME, and click on it. Then, click on the blue Add button at the extreme right corner of the table header under the chosen record type.

The Time-To-Live (TTL) attribute is an important setting that specifies the total number of seconds the local resolver ought to cache the response for a record before requesting a new one. The default TTL is 86400 seconds, but you can modify it as per your domain's requirements.

To configure multiple hosts to provide responses for a domain, click on Add IP after each entry. This allows you to configure multiple hosts for a DNS record.

Here are the steps to create a new record in DDI Central:

Monitoring managed zones is crucial to ensure the reliability and performance of your DNS infrastructure. Cloud DNS offers logging for all queries to managed zones through Logging.

You can use this feature to track the status of ALIAS name resolution, which is not available from the DNS response. The alias_query_response_code is an optional field in the DNS query log that records this information.

A value of NoError in the alias_query_response_code means that the ALIAS record was resolved successfully. Any other value represents an error.

Here's a breakdown of what the SERVFAIL value can represent: