DNS management

Creating a zone#

A zone represents a domain you want to manage. In the console, go to DNS → Create Zone and enter your domain (e.g. example.com). Edge will generate nameservers for you, which you’ll need in the next step.

You can create multiple zones for different domains or subdomains. Each zone is independent with its own set of records.

Updating nameservers at your registrar#

For Edge to serve DNS for your domain, point it at our nameservers. At your domain registrar (where you bought the domain), find the DNS or nameserver settings and replace the current nameservers with Edge’s.

Edge provides two nameservers, e.g. ns1.edge.network and ns2.edge.network. Propagation can take up to 48 hours, though it’s often much faster.

Adding A, AAAA, CNAME, MX and TXT records#

• A records: map a hostname to an IPv4 address. Use them for your main domain or subdomains pointing to servers.
• AAAA records: map to IPv6 addresses. Add both A and AAAA for dual-stack support.
• CNAME records: alias one hostname to another. Use them for www pointing to your root domain, or for CDN origins.
• MX records: define mail servers. Add these when using external email providers (e.g. Google Workspace, Fastmail).
• TXT records: store text, commonly used for domain verification, SPF, DKIM and other authentication.

Understanding TTL#

TTL (Time to Live) controls how long resolvers cache your records. A low TTL (e.g. 60 seconds) means changes propagate quickly but increases DNS query load. A high TTL (e.g. 3600) reduces queries but slows propagation.

Use low TTL before migrations; use higher TTL for stable production records.

Geo-routing#

Edge DNS supports geo-routing, which serves different answers based on the requester’s location. Use this to direct users to the nearest region or to comply with data residency requirements.

In the record editor, enable geo-routing and add region-specific values. For example, EU users might get a different IP than US users.

Monitoring DNS metrics#

Each zone has a metrics dashboard showing query volume, response times, and record hit rates. Use these to understand traffic patterns and identify anomalies.

Access metrics from the zone detail page. Set up alerts for unusual spikes or errors.