Names, labels, and fully qualified names

A DNS name is made of labels separated by dots. Read api.shop.example.com from right to left.

Starting at the right, com is below the DNS root, example is below com, then come shop and api. The dots separate labels; they are not part of a label.

The root is represented by the final dot in the complete form:

api.shop.example.com.

That absolute name is a fully qualified domain name, or FQDN. It identifies the same DNS name regardless of a machine’s local search suffix.

A name without the final dot can be treated as relative in some tools and configuration files. On a company network, printer might be expanded to printer.office.example.com. This convenience can also make debugging confusing because the displayed input is not necessarily the question sent to DNS.

Zone editors add another kind of relativity. Inside the example.com zone, a dashboard may expect api.shop and append the zone automatically. Another interface may accept the full name. Check its preview so you do not accidentally create api.shop.example.com.example.com.

DNS names are case-insensitive for lookup purposes, but the application reached through the name can have case-sensitive URLs or data. Also avoid assuming that every label below a suffix is independently registrable; registration policy and public suffix rules are separate from DNS hierarchy.

Compare absolute and displayed forms:

dig A api.shop.example.com.
dig A api.shop.example.com

They normally ask the same question when no search behavior intervenes. The trailing dot makes the intent explicit.

Your action is to split cdn.assets.shop.example.com. into labels, identify the root and likely zone apex, then write the relative owner name you would enter inside an example.com zone editor.