---
title: "Add your first domain"
description: "Step-by-step guide to adding a domain to Edge DNS: create a zone, point your registrar at your unique nameservers, verify ownership, and add DNS records."
url: "https://edge.network/docs/dns/getting-started"
section: "DNS"
---

# Add your first domain

This guide walks you through adding a domain to Edge DNS and verifying ownership.

## Prerequisites

- An Edge Network account ([sign up here](/console/access/new))
- A domain name you own or manage
- Access to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.)

## Set up your domain

### 1. Create a DNS zone

A zone represents your domain in Edge DNS. Each domain you want to manage needs its own zone.

1. Navigate to **DNS** in the sidebar.
2. Click **Add Zone**.
3. Enter your domain name (e.g. `example.com`).
4. Click **Create Zone**.

![DNS zones list in Control](/media/docs/control-dns-zones.svg)

> [!NOTE]
> **Zone vs subdomain.** Create a zone for your root domain (`example.com`). Subdomains (`www`, `api`, `blog`) are managed as records within the zone.

### 2. Note your unique nameservers

After creating your zone, you'll be shown your unique Edge nameservers. These are specific to your account and must be used for all domains.

Your nameservers will look like this:

```text
ns1-abc123.edge.network
ns2-abc123.edge.network
```

The `abc123` part is unique to your account.

> [!WARNING]
> **Keep your nameservers secure.** Your unique nameserver pair ensures only you can add domains to your account. Never share it with untrusted parties.

### 3. Update your domain registrar

Log in to your domain registrar and update the nameservers for your domain.

Common registrars:

- **GoDaddy:** My Products → Domain → Manage → Nameservers → Change
- **Namecheap:** Domain List → Manage → Nameservers → Custom DNS
- **Cloudflare:** Domains → Manage → Update DNS configuration
- **Google Domains:** DNS → Name servers → Use custom name servers

> [!NOTE]
> **Propagation time.** DNS changes can take up to 48 hours to propagate globally, though most updates complete within a few hours.

### 4. Verify nameservers

Once you've updated your registrar, verify the change in the Edge console.

1. Return to your zone in the Edge console.
2. Click **Verify Nameservers** or **Check Nameservers Now**.
3. Wait for confirmation (usually a few seconds).

> [!TIP]
> **Zone activated!** Once verified, your zone status changes to **Active** and Edge DNS begins serving queries for your domain.

If verification fails, the console shows the nameservers it currently detects. Wait a few more minutes for propagation and try again.

### 5. Add DNS records

With your zone active, you can now add DNS records.

1. Click the **Records** tab in your zone.
2. Click **Add Record**.
3. Select the record type (A, CNAME, MX, etc.).
4. Enter the record details and click **Add**.

![Records tab of a DNS zone in Control](/media/docs/control-dns-records.svg)

Common first records:

| Type | Name | Value |
|---|---|---|
| `A` | `@` | `185.x.x.x` |
| `CNAME` | `www` | `example.com` |
| `MX` | `@` | `mail.example.com` (priority 10) |

## Test your DNS

Verify that your records are resolving correctly:

```bash
# Check A record
dig example.com A +short

# Check all records
dig example.com ANY

# Query Edge DNS directly
dig @ns1-abc123.edge.network example.com A
```

## If you don't have a domain

If you don't have a domain yet, you can register a **test.network** subdomain for $1/month. Navigate to **DNS → test.network** in the console, pick a subdomain name (e.g. `my-project.test.network`), and the DNS zone is created instantly. No registrar configuration is needed. You get full control over the zone (A, AAAA, CNAME, MX, TXT records, etc.).

See [test.network domains](/docs/dns/test-domains) for full details.

## Next steps

- [DNS records](/docs/dns/records) — Learn about all record types
- [Geographic routing](/docs/dns/geo-routing) — Route traffic by location
- [Metrics and analytics](/docs/dns/metrics) — Monitor query volume and latency
- [Nameserver security](/docs/dns/nameservers) — How unique NS pairs protect you