Records, aliases, and query type | DNS: understand and diagnose resolution

Concept and mechanism

DNS associates names with typed record sets. A represents IPv4 addresses and AAAA represents IPv6. CNAME indicates an alias targeting another name; PTR is used in reverse address-to-name lookups. Do not assume an A query demonstrates the AAAA result or that reverse mapping exists merely because a forward record exists. An application preferring IPv6 may follow a different path from support’s IPv4 test.

Guided application

Before changing a record, identify the type actually used and the name chain followed by the client. An alias may be correct while targeting a name that no longer exists. Ordinary DNS rules do not allow CNAME to freely coexist with other data at the same name; vendor alias or flattening features need separate analysis. A zone apex has required data such as SOA and NS, so copying a subdomain CNAME pattern may fail. Always distinguish protocol rules from vendor-specific functionality.

IN PRACTICE

An IPv4 test works, but IPv6 clients reach an old deployment through AAAA. Fixing A alone does not address the affected path.

Common pitfalls

Querying one type and generalizing to all; forgetting a CNAME target; assuming PTR is automatically created with A.

Related topics: TTL, negative caching, and controlled change · NXDOMAIN, NODATA, SERVFAIL, and timeout

Take this idea with you

Record type and name chain are part of diagnosis, not incidental details.

Create account

Reference: RFC 2181: DNS clarifications · DNS RFC 1034/1035 with RFC 2181, 2308, 3596, 4033, 7766 and 8767; dig BIND 9.20