Visual RFC.
ALL RFCs / RFC 1034
Read the RFC ↗
RFC 1034 / NAMES & RECORDS

Aliases

07

An alias redirects DNS resolution to a canonical name, where the desired record can be found.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 1034 · § 3.6.2EXAMPLE
4 / 4
AliasesThe query visibly follows the CNAME target before locating the requested address.Question: A www.example.org.www.example.org.CNAME service.example.org.follow targetservice.example.org.A 192.0.2.20Answer includes the alias and the target address
04
Return the complete result.

The application can use the address while the resolver caches the relevant records.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Follow the name, then answer the type.

  • For a non-CNAME question, include the CNAME and restart at its target.
  • A query specifically for CNAME returns the alias record itself.
  • Detect alias loops and signal an error rather than looping indefinitely.
DETAILS

RFC 1034 says a CNAME owner should have no other data. Later DNSSEC specifications add carefully defined exceptions for DNSSEC records.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. The name tree
  2. Resource records
  3. Delegation & glue
  4. Iterative resolution
  5. Recursive resolution
  6. Caches & TTL
  7. Aliases
  8. Missing names & failures
  9. Wildcard synthesis
  10. Zone maintenance
  11. Reverse lookups
  12. Transport & historical scope

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗