A domain of your own¶
By default a zone's files live under the service's hostname, with the zone as the first path segment:
Give the zone a hostname and the same file is:
Nobody else's name in the URL, and one fewer path segment.
Setting it up¶
- Point a CNAME at the service:
assets.acme.com→cdn.example.com. - Put the hostname in Hostname of its own on the zone's settings page.
- Arrange a certificate for it on whatever terminates TLS in front.
Both spellings keep working afterwards — the hostname is an addition, not a move, so links you have already handed out do not break.
What changes on that hostname¶
The whole path is the object's name, because the hostname has already said which zone this is. That makes https://assets.acme.com/favicon.ico reachable, which the service's own hostname cannot express: there the first segment is the zone, so every object needs at least two.
It also means a request for /another-zone/x on your hostname asks your zone for an object at that path. It is not a way into the other zone.
Everything else is unchanged: a private zone still wants a signature, referrer and CORS rules still apply, preflight requests are answered for the right zone, and traffic is counted against the zone the hostname belongs to rather than against whatever the first path segment happened to be.
One hostname, one zone¶
A hostname answers for one zone or for none — the column is unique, and claiming one another zone already has is refused with a message rather than a server error. Clear the field to give it up.