Authoritative DNS, on name servers we run.LIVE
Zones on our own name servers in more than one region, every record type, changes live within seconds, zone transfers between accounts, verification that turns a zone active by itself when the registry points at us, and the whole thing from the console and the API.
What happens when someone looks up your name.
- 01
You add the zone
From the console or <code>POST /api/v1/dns/zones</code>. The zone is created on every name server of the cluster at once, with our name servers listed for you to set at the registrar.
- 02
You add records
A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, PTR and the rest, with TTLs and priorities; a change is on every server within seconds.
- 03
The registry points at us
The platform asks the parent zone which name servers the domain is delegated to; the moment it is ours, the zone turns active by itself.
- 04
Resolvers get answers
Authoritative answers from the nearest name server, served from our own address space behind the same DDoS filtering as everything else.
- 05
Hand it over when you need to
Offer a zone to another Joy account; they accept, the records move, nothing resolves differently for a second.
The same answers from every name server.
Every domain you run
One place for the zones of every site and service, next to the servers they point at.
SPF, DKIM, DMARC
The TXT and MX records mail needs, changed in seconds when a provider changes.
Records from your pipeline
Create a server, add its A record, issue a certificate — from one API token.
Which name servers do I set at my registrar?
The ones the console shows on the zone page; they are the same for every zone. The zone turns active by itself once the registry lists them.
Can I move a zone to another account?
Yes: offer it from the zone page; the other account accepts it under Zone transfers and the zone, with every record, is theirs.