Visual RFC.
ALL RFCs / RFC 1034
Read the RFC ↗
RFC 1034 / EDGE CASES

Wildcard synthesis

09

DNS wildcards synthesize records under specific tree-matching rules; they do not replace every matching string.

Related RFCs and changes

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

RFC 1034 · § 4.3.3EXAMPLE
4 / 4
Wildcard synthesisA missing branch selects wildcard data and creates a record whose owner is the actual queried name.example.org.*A 192.0.2.20existingA 192.0.2.30Question: new.example.org. Anew.example.org. A 192.0.2.20Synthesized owner; wildcard dataExact existing names win; zone cuts stop parent synthesis
04
Return the synthesized record.

This is an answer generated by DNS tree rules, not a web-server redirect.

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

Tree existence controls wildcard use.

  • An exact name match takes precedence over wildcard synthesis.
  • Delegation boundaries prevent a parent wildcard from answering inside a child zone.
  • Synthesis uses wildcard data but sets the answer owner to the queried name.
DETAILS

RFC 4592 later clarifies wildcard terminology and behavior. This chapter illustrates the original concept; it is not a full implementation algorithm.

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 ↗