Host your domains' DNS on CubePath's anycast network, with GeoDNS and health checks. Manage zones on the DNS Zones page in my.cubepath.com.
How it works
A zone is one domain and every record under it. You create the zone here, point the domain's nameservers at CubePath at your registrar, and from then on our nameservers are the authority for that name: every resolver in the world asks us, and we answer from the anycast network — the same addresses announced from every location, so a query is answered by whichever site is closest to the resolver that sent it.
That's also what makes the two features on top of it work. Because we answer the query rather than handing out a static file, the answer can depend on where the resolver is (GeoDNS) and on whether the target is alive (health checks).
Create a zone
- 1Add the domainClick Create Zone and enter your domain (e.g.
example.com), withoutwww. - 2Choose how to startEmpty zone and add records by hand, upload a zone file (BIND format —
.txt,.zoneor.db, up to 1 MB), or quick scan to look up the records your domain publishes today and import what we find. - 3Point your nameserversAt your registrar, set the domain's nameservers to the CubePath nameservers shown on the zone's Nameservers tab.
- 4VerifyCome back and click Verify. Once the delegation is visible, the zone goes active and starts answering.
ImportantImport or scan before you change the nameservers, not after. Delegating a domain to an empty zone means every name under it stops resolving the moment the change propagates.
A zone reports one of: pending verification (created, delegation not seen yet), verification failed (we looked and the nameservers weren't ours), active (serving), suspended (not serving — contact support for the reason) or deleting.
The zone tabs
| Tab | What it's for |
|---|---|
| Records | Every record in the zone: names, types, values and TTLs |
| Nameservers | The nameservers to set at your registrar, and the Verify button |
| SOA settings | Zone-level timers and the hostmaster contact |
| Health checks | Probe a record's target and pull it from DNS when it fails |
| Recommendations | One-click SPF, DKIM and DMARC records for your domain |
| Activity | Audit log of every change to the zone |
GeoDNS isn't a tab of its own — it's a field on each A/AAAA record, so it lives in Records.
Plans
| Plan | GeoDNS | Health checks | Zones | Records per zone | Min TTL |
|---|---|---|---|---|---|
| Free | No | 0 | 3 | 50 | 60 s |
| Pro | Yes | up to 10 | 10 | 200 | 30 s |
| Business | Yes | up to 50 | 50 | 1000 | 10 s |
Each health check is billed at $10/month, prorated and stopped the moment you delete or disable it.
What it doesn't do
- GeoDNS routes by the resolver's location, not by load. It sends a whole region to one answer set; it doesn't spread requests by server load. For per-request balancing inside a region, use a Load Balancer.
- A health check watches one IP, not a service. Three servers means three records and three checks.
- DNS failover isn't instant. Resolvers cache your answers for the length of the TTL, whatever we know in the meantime.
Delete a zone
Deleting removes the zone and all its records, and can't be undone — the dialog asks you to type the domain to confirm. Move the delegation somewhere else first: once the zone is gone, our nameservers stop answering for the domain, and if the registrar still points at them, the domain stops resolving entirely.
TipKeep your own copy of any zone that matters — a zone file in your repository is the cheapest insurance there is. A quick scan only finds what the domain publishes right now, so it's a migration tool, not a backup.