# About DNS

> InfraNest manages the DNS for all your domains in one place, whichever provider hosts it.

Source: https://infranest.io/docs/dns
Last updated: 2026-09-14

---

This article explains how InfraNest handles DNS for your domains, and who should read it if they manage domains, email, or website security settings.

## Overview

- InfraNest manages the DNS for all your domains in one place, no matter which provider hosts them.
- Import your zones, edit records in a single consistent editor, and InfraNest pushes the changes to the provider for you.
- It also keeps an eye on drift, security gaps, and what the internet actually sees for your records.

## What you can do

- **One editor for every provider.** Zones from Cloudflare, Amazon Route 53, Hetzner, TransIP, GoDaddy, IONOS and Namecheap all live together in InfraNest, edited the same way.
- **Two-way sync.** Records you change in InfraNest are pushed to the provider; records changed at the provider are pulled back into InfraNest. If something changed outside InfraNest without going through the sync, it's flagged so you can see it.
- **Keep DNS and email secure.** A built-in security check looks at each zone for SPF, DMARC, DKIM, MX, DNSSEC and CAA, and tells you what's missing.
- **Roll out standard records with Templates.** Save a working set of records and apply it to any zone.
- **We check what the internet actually answers.** From time to time, InfraNest asks public DNS servers what they return for your records and compares that with what's stored in InfraNest. If they differ, you get an email naming each record — its name, its type, what InfraNest holds, and what the resolvers are answering right now — with a link straight to the zone. Nothing is changed automatically; the email just tells you what visitors and mail servers are currently being told.
- **Manage whole zones.** Discover, create and delete zones, copy records between zones, or import by scanning live DNS.

## Find the DNS page

1. Open the sidebar and select **DNS**.
2. You'll see a list of all your zones across every provider, showing **Status**, **Provider**, record count, and when each zone was last synced.
3. Use **Search** or **Filter** to narrow the list, or **Add tag…** to organize zones with **Tags**.
4. Select **Discover zones** to find zones already set up at a connected provider, or select **Create** to start a new zone.
5. Select any zone in the list to open it and manage its records.

## Understand two-way sync and drift

1. When you change a record in InfraNest and select **Save changes**, InfraNest pushes that change to the provider.
2. When someone changes a record directly at the provider, InfraNest pulls that change back in during the next sync.
3. If a record was changed outside InfraNest in a way that hasn't synced yet, it shows up as **out of sync** or **Not yet synced to provider** so you know to review it.
4. Use **Sync this zone** to refresh a zone on demand rather than waiting for the next automatic check.

## Check what the internet actually sees

1. InfraNest periodically checks public DNS servers to see what they return for your records.
2. If the live answers differ from what's stored in InfraNest, you'll receive an email listing each affected record, its type, the stored value, and the live value.
3. Open the link in the email to go straight to the zone in InfraNest.
4. From the zone, use **Check propagation** or **Verify live** to see the current picture, and **Show stored** to compare against what InfraNest has saved.
5. Nothing changes automatically — decide whether to **Send mine to the provider** or **Overwrite with live values** based on what you find.

> [!NOTE]
> These checks only report differences by email — they don't change any records for you. You choose what to do next from the zone page.

> [!TIP]
> Save a set of records you use often as a template under **DNS Templates**, then use **Apply template** to roll it out to any zone in seconds.

<!-- docs-screenshots:start -->

![About DNS](/media/cdfb8a82-590f-4679-889e-3ba4e881e875)

<!-- docs-screenshots:end -->
