ZoophostDocs

Edit DNS records

Manage zones and records on Zoophost nameservers: supported types, TTL rules, CNAME conflicts and the record quota.

Domains & DNS4 min read

Zoophost runs authoritative DNS on its own nameservers. A zone is a domain's record set; the editor is in the console under Domains & DNS.

Open a zone

Console → Domains & DNS → a zone → the record editor. The header shows the nameservers and record count.

Alternatively, open a domain from the Domains page and choose Manage DNS zone.

Supported record types

A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR.

The editor also accepts ALIAS through the API, but the published DNS policy lists the nine types above; stick to those unless support tells you otherwise.

Add a record

  1. Choose Add record.
  2. Pick the Type.
  3. Enter the Name — @ for the apex, or the subdomain without the zone name.
  4. Enter the Value.
  5. For MX and SRV, set Priority.
  6. Set TTL in seconds.
  7. Choose Save record.

Examples:

Type Name Value TTL
A @ the IPv4 address in your console 300
A app the same address 300
CNAME www @ 3600
MX @ 10 mx.webspeed.online 3600
TXT @ v=spf1 include:spf-c.mailbaby.net ~all 3600

TTL and propagation

  • TTL must be between 30 seconds and 7 days (604800). The default is 3600.
  • Lower TTLs (300 or less) are better while you are making changes.
  • Existing clients cache the old answer until its TTL expires. A record change is not visible everywhere at once.

If you are migrating from a provider with long TTLs, lower the TTL a day before the change, then raise it after.

Rules and limits

  • 200 records per zone. More can be discussed with support.
  • CNAME cannot share a name with any other record. Use an A/AAAA record at the apex instead.
  • Renaming a record creates a new record and removes the old one. There is no partial “move”; check both names afterward.
  • Zone creation in the console publishes the mail record set and an apex A record automatically. That is convenient for a new site and surprising if you only wanted a web zone: the zone will advertise an MX that points at the mail host even before mailboxes exist. If you do not want that, remove the mail records or use a zone created for a purchased domain, which does not add them automatically.

Purchased-domain zones

A domain bought or transferred through Zoophost gets a zone with:

  • An A record at the apex pointing at Zoophost.
  • A CNAME for www pointing at the apex.
  • No mail records until you set up email.

This is the safe default. Add records as you need them.

Point a domain at a service

Cloud app — prefer Host this domain here on the app's Domains card when the zone is on Zoophost nameservers. It writes the exact A record at TTL 300. If the zone is elsewhere, the console shows the record to create.

VPS or dedicated server — create an A record pointing at the machine's IPv4 address. Keep the reverse DNS record (PTR) consistent if you run mail.

Object storage — Z2 has its own endpoint; you do not usually point a DNS record at it. Use presigned URLs or your app in front.

Verify

dig +short app.example.com A
dig +short example.com MX
dig +short example.com TXT

Query a public resolver as well as the authoritative nameserver. If they disagree, the answer is cached or the delegation has not propagated.

Common problems

The record saves but the site does not load — check the value against what the console expects, and confirm you edited the zone that actually serves the domain.

CNAME rejected — another record already exists at that name. Delete it first.

Mail stops after a DNS change — an MX or SPF record was removed. Restore it from Mail DNS and deliverability.

Delegation check fails — the registrar still announces different nameservers. See Nameservers and delegation.

Next

  • dns
  • zone
  • record
  • a record
  • cname
  • mx
  • txt
  • ttl
  • nameserver

Ready to use this

Authoritative DNS with a full record editor and one-click mail records.

  • Works with a domain registered anywhere
  • No uptime SLA, stated plainly
Manage DNS with us
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.