Skip to content

DNS

Host your domains' public DNS on EZGH Cloud, with record sets and DNSSEC, managed through the console, the API and the ezgh CLI.

Updated View as Markdown

EZGH DNS answers public DNS queries for your domains. A zone holds one domain’s records, in a project, and has two nameservers of its own. You manage it in the console, through the DNS API and with ezgh dns.

Concepts

Term Meaning
Zone One domain’s public DNS, in a project. Zones aren’t regional. Resource type zon.
Record set The records at one name and type, with one TTL.
Nameservers The two hostnames that answer for a zone, <label>.ns1.ezghdns.org and <label>.ns2.ezghdns.org for .com and .net domains, and <label>.ns1.ezghdns.com and <label>.ns2.ezghdns.com for the rest. Each zone has its own.

Going live

A zone answers once you prove you control its domain. Either of these does it:

  • A TXT record at _ezgh-challenge.<domain>, with the zone’s value, published at your current DNS provider. Use this for a domain that’s already live elsewhere: see Move a domain with no downtime.
  • The domain’s nameservers at your registrar, set to exactly the zone’s two. Use this for a new domain: see Get started.

A pending zone is checked about every minute for its first hour, then hourly, and checks stop after 14 days. ezgh dns zones verify, or VerifyZone, runs one at any time.

Zone status

Status Meaning
pending Waiting for proof of control. Records can be added, and aren’t served yet.
active Answering. Losing the delegation at your registrar doesn’t change this.
displaced Not answering. See below.
deleting Being removed from the nameservers. It then stops existing.

A domain can have only one active zone at a time, though it can be pending in several zones and organizations. If another zone proves control of an active zone’s domain, the active zone becomes displaced: it stops answering, and its records stay until you delete it. A displaced zone isn’t checked on its own: run a check to prove control again and bring it back. A signed zone can come back with new DS values, so compare them with the DS at your registrar.

A zone for a subdomain of a domain active in another organization answers only while that parent zone delegates it with an NS record. If the parent removes the record, or goes active without one, the subdomain’s zone becomes displaced.

Zones can’t be created for public suffixes such as com or co.uk.

A zone that serves a domain registered in EZGH Domains can’t be deleted, and its DNSSEC can’t be turned off, here: both are refused with 409 managed_by_domains. Turn DNSSEC off from the domain. To delete the zone, move the domain to nameservers of your own first. See Manage a domain.

Permissions

DnsFullAccess manages zones and records; DnsReadOnlyAccess views them. See Managed policies for every action.

Trails

DNS records its changes in Trails with eventSource dns.ezghcloud.com: CreateZone, DeleteZone, VerifyZone, EnableZoneDnssec, DisableZoneDnssec and ChangeRecordSets, and the service events ActivateZone and DisplaceZone, the latter with the reason. Events name the zone and each record set’s name and type, never its values.

Quotas

See DNS’s default quotas.

Pricing

DNS is free.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close