A domain name is also a delegation path. The label tree is recomputed from the exact QNAME bytes, so the hierarchy is not hand-authored.

highlighted = computed this step

Why the tree reads right to left

A DNS name is written left to right for people, but delegation works from the root toward the specific host. The tree is recomputed from the same QNAME bytes.

rootTLDname\text{root}\to\text{TLD}\to\text{name}
www.example.comThe DNS name hierarchy is recomputed from the QNAME bytes.www.example.com - 17 byte QNAME.comexamplewww

Root to host

The parsed labels become root dot, com, example, then www. No independent tree labels are trusted; the bytes decide the nodes.

.comexamplewww.\to\text{com}\to\text{example}\to\text{www}
www.example.comThe DNS name hierarchy is recomputed from the QNAME bytes.www.example.com - 17 byte QNAME.comexamplewww

Decode it again

The second QNAME uses mail, openai, and com. The same parser reverses those labels into the delegation tree.

.comopenaimail.\to\text{com}\to\text{openai}\to\text{mail}
mail.openai.comThe DNS name hierarchy is recomputed from the QNAME bytes.mail.openai.com - 17 byte QNAME.comopenaimail

Summary

The hierarchy is not a separate drawing; it is parsed from the exact QNAME bytes. Message structure and exact bytes only; resolution timing, caching, and UDP/TCP transport are not modeled here.

labels parsed from QNAME\text{labels parsed from QNAME}
www.example.comThe DNS name hierarchy is recomputed from the QNAME bytes.www.example.com - 17 byte QNAME.comexamplewww