Change your DNS without fear, and catch mistakes before anyone notices.
InfraNest shows what a change touches before you save it, and whether it worked after. It also finds the problems you did not cause: a record changed elsewhere, a name pointing at a deleted server, email anyone can fake.
See what a DNS change will touch before you save it
A DNS edit feels risky because nothing tells you what hangs off that one line. InfraNest does. Before you save, it names every monitor, certificate and record that depends on it. After you save, it shows where the new address has arrived and whether your site still works. If it looks wrong, undo it right there.
Says how long visitors may see the old address
Deleting a record names what stops working
Undo reaches back 30 days on Free, a year on Business
Edit A record for northwyndr-app.dev
Points to
198.51.100.21Your server api-02
4 things depend on this record
Monitor App — northwyndr-app.dev checks this name. After the change it checks whatever the new value answers.
Certificate northwyndr-app.dev covers this name. Its renewal has to reach the new target.
app.northwyndr-app.dev follows this record and changes with it.
api.northwyndr-app.dev follows this record and changes with it.
Save change
After saving
northwyndr-app.dev will point to api-02 — resolvers may keep the old value for up to 4 more minutes.
Saved at Cloudflare 1 minute ago. Where the internet sees it:
Cloudflare nameserversNew address
Cloudflare public DNSNew address
Google public DNSOld address, for up to 4 more minutes
Monitor “App — northwyndr-app.dev”: up since the change, responding in 184 ms, certificate valid.Undo change
Find out when someone changes a record outside InfraNest
Most DNS trouble starts with a change nobody remembers: a colleague in the provider’s panel, a plugin, an old script. InfraNest compares each zone with what your provider holds, and with what the internet answers. You see what the record was, what it is now, where it changed and when. Then you keep the new version or put yours back, one record at a time.
Someone changed these at Cloudflare itself — in its dashboard or with an API key — not here. That can be a fix or a mistake, so decide per record which version stays.
nowChanged the A record wwwOutside InfraNestnorthwyndr.de · at Hetzner
nowChanged the A record @northwyndr.de · by Alex Rivera
5 hours ago2 records changed at onceOutside InfraNestnorthwyndr-docs.com · at Cloudflare
5 days agoOffice — Amsterdam IP changed 1 time, now 198.51.100.23northwyndr.com · dynamic IP
Never leave a name pointing at a server you deleted
When you delete a server, your provider soon gives its address to someone else. Any name still pointing there then shows a stranger’s site under your name. InfraNest stops this first. Before a server goes, it lists the names pointing at it, and you move, remove or keep each one. If a server left another way, the record is flagged on the zone, the DNS overview and Home.
The editor refuses a new record on that address
Also flags names left on a service you stopped using
Nothing changes until you choose
Delete server · staging-web-01
1 address points here: staging.northwyndr-app.dev
When this server is deleted, the provider gives its address to another customer — and any name still pointing at it will show their site instead of yours.
Astaging.northwyndr-app.dev192.0.2.10
Move to another serverRemove the recordKeep it
northwyndr-docs.com
preview.northwyndr-docs.com points at an address you no longer have
The server behind this address was deleted, and the provider gives that address to its next customer within days — often the same week. Until then the name resolves to nothing; after that it resolves to a stranger's machine, and anyone visiting the name reaches them instead of you. People scan the internet for exactly this. Point the record somewhere you control, or remove it.
A preview.northwyndr-docs.com → 198.51.100.77 — docs-02 left your fleet on 19 Oct 2026
Open zone
nwyndr.ioAnyone can take over blog.nwyndr.io
Know why a name will not resolve, without digging
A site that cannot be found has several possible causes, and each needs a different fix. When a monitor cannot look up a name, InfraNest asks the internet why. The alert and the incident then say it in one line: the domain expired, the nameservers stopped answering, a record was removed. If your DNS is fine, it says that too. A record deleted at your DNS provider is named as the likely cause.
Works for names hosted anywhere
Needs a monitor on that name
Monitors are included on every plan
Staging apphttps://staging.northwyndr-app.devDown
Why it doesn’t resolve
staging.northwyndr-app.dev no longer exists at its nameservers
It resolved in earlier checks, so the record was removed or renamed.
Likely cause
The DNS record for staging.northwyndr-app.dev was deleted at your DNS provider
Cloudflare · 9 minutes ago
Other answers the same check can give
northwyndr-app.dev has no nameservers on the internet
None of the nameservers for northwyndr-app.dev answered
DNSSEC for northwyndr-app.dev is broken
staging.northwyndr-app.dev resolves fine from public DNS
Stop strangers sending email as you, in one click
Without the right DNS records, anyone can send mail in your name, and it may still arrive. InfraNest checks every zone and says so in plain words. It builds the SPF and DMARC records from the mail provider you use, shows you each one, and writes them when you agree. CAA, which limits who can issue certificates for you, works the same way. Connected to both your DNS host and your registrar? DNSSEC is one press too.
DMARC starts by watching, so delivery does not change
DKIM comes from your mail provider; InfraNest checks it
Nothing tells receiving servers what to do with mail that fails your checks, so anyone can send as you and it will still land.
Protect mail from this domain
Mail for this domain is handled by Google Workspace.
SPFAdd
Allows your mail provider to send for this domain.
TXT @ v=spf1 include:_spf.google.com ~all
DMARCAdd
Tells receivers what to do with mail that fails SPF and DKIM.
TXT _dmarc v=DMARC1; p=none
Write 2 records
CAANo CAA recordsFix this →
DNSSECDNSSEC is offTurn on DNSSEC
Move your DNS to another host, checked before the switch
Moving DNS usually means copying records by hand and hoping you missed none. InfraNest creates the zone at the new host and copies every record. Then it asks the old and the new nameservers for every name. Nothing changes at your registrar until the answers match. If one differs, the move stops and shows you which name. You can close the page while it runs.
Moving DNS is on Pro and up
Your registrar has to be connected too
The old zone stays where it is
Move the DNS of 2 domains to another host
1.Create the zone at the new host.
2.Copy every record from the zone InfraNest holds.
3.Ask the old and the new nameservers for every name, and stop if any answer differs.
4.Point the domain at the new nameservers at its registrar.
5.Check until the internet asks the new host. The old zone stays where it is.
The new host answers some names differently, so nothing was switched.
app CNAME: was northwyndr-api.dev, the new host answers —
Everything else it handles
The parts that are only interesting when you need them.
One editor for every provider
Every DNS provider works the same way here. The form asks for what each record type needs and checks it as you type, so a private address on a public record or a broken SPF line gets caught before it goes live.
Records in plain words
Records are grouped by what they do: your website, your email, everything else. Each one says what it points at and what uses it, and you can leave a note on it. Notes stay in InfraNest and are never published.
Find any record in any zone
Search every zone at once by name, value, IP address, server or service such as Google Workspace.
Move records to a new server in one go
Pick the old server and the new one. Every record pointing at it, in every zone, moves in one change, and you can undo the whole move from History.
A history of every change
Each zone lists who changed what and where, with a way back. History goes back 30 days on Free, 90 on Pro and a year on Business.
Changes that never reached anyone
If your registrar points the domain at another host, whatever you save here reaches nobody. InfraNest says so on the zone and on the overview, and names where the internet is really asking.
Leftovers, tidied after you agree
Old verification codes, addresses that have not answered for 90 days and second copies are listed record by record. Nothing is removed until you confirm, and you can undo it.
Templates, built-in and your own
Apply Google Workspace, Microsoft 365 or a security baseline, or save any zone as a template. A preview shows every record first, and flags anything it would replace. On Pro and up.
Zone files in and out
Download any zone as a standard BIND file, or import one. You see what will be added and every line it had to skip. An import only ever adds.
Try a change through the API
Add dry_run=1 to a record or template call and the API answers with what would change. Nothing is saved or sent. The API is on Pro and up.
A record that follows a changing address
Pick a home or office connection and a record follows it. Your router reports the Dynamic IP once, and InfraNest updates every record that depends on it.
Rules for new domains
A rule can create the zone and apply a template when a domain arrives. You write the rule once and see every run. Templates in automations are on Pro and up.
See what needs you in your DNS, in about two minutes
Connect one provider with an API key. Nothing changes at the provider until you say so.
Nine modules are on every plan, Free included, and firewalls start on Pro. What changes is how much of each you get, plus a few advanced features from Pro.
Cloudflare, AWS Route 53, Hetzner, DigitalOcean, IONOS, TransIP, GoDaddy, Namecheap, OVH, Porkbun, Dynadot and Openprovider, with more added regularly. The integrations page lists exactly what each provider’s API supports.
Do I have to move my DNS to InfraNest?
No. InfraNest edits your zones where they already are. Your nameservers stay with your provider and nothing is migrated. You get one place for all of them instead of a panel each.
Will connecting InfraNest break my site?
No. Connecting a provider only reads your zones. Nothing at the provider changes until you save something, and you see what it touches first. You can disconnect the key at any time.
How do I know if someone changed my DNS records?
InfraNest compares each zone with what your provider holds, and shows every record changed outside it: what it was, what it is now, where and when. It cannot name the person behind a change made at the provider. Edits made inside InfraNest do show who made them. It also asks public resolvers whether they answer what is stored. Alerts on these changes are on Pro and up, by email, Slack, Teams, Discord, Telegram or PagerDuty.
Why is my domain not resolving?
The usual causes are an expired domain, nameservers that stopped answering, broken DNSSEC or a removed record. Put a monitor on the name and InfraNest finds out which one when it fails, and says so in the alert and the incident.
Can I undo a DNS change?
Yes. After you save, Undo sits right beside the change. Later, History lists every change with a way back: 30 days on Free, 90 on Pro and a year on Business. If the record has changed again since, InfraNest says so instead of overwriting it.
What happens to DNS records when I delete a server?
They keep pointing at its address, and your provider gives that address to someone else, often within days. Delete a server in InfraNest and it first lists those names, so you can move, remove or keep each one. If a server left another way, the records are flagged. InfraNest never changes them on its own, because only you know what should go.
How do I set up SPF and DMARC?
Open the zone’s Protection tab. InfraNest recognises your mail provider, or asks you to pick it, and shows the SPF and DMARC records it would write. Your existing SPF record is kept and your provider is added to it. DMARC starts by watching, so delivery does not change, and you make it stricter when you are ready. This works on every plan.
How do I move DNS to another provider safely?
Connect both the new host and your registrar, then choose Move DNS. InfraNest copies every record and compares the old and new nameservers name by name. It changes your registrar only when they match, and it stops and shows the difference when they do not. Moving DNS is on Pro and up.
Can any of this run on its own?
You choose. A rule can create a zone and apply a template when a domain arrives. A rule can also start when records change at the provider or stop matching live DNS, for example to send an alert. Every run is listed. Putting a changed record back stays your decision.
Can I apply DNS templates?
Yes, on Pro and up. There are built-in presets for Google Workspace, Microsoft 365 and security baselines, plus any template you save from your own zone. A preview shows every record first, and flags anything it would replace.
See what needs you, before your visitors do
Connect a provider and get your zones, your first findings and the email check within minutes.
Free plan · No credit card required · Set up in minutes
Your privacy, your choice
We use only what’s needed to keep InfraNest running. With your permission, we’d also like to understand how our website is used so we can improve it, and follow up properly when you write to us.
You’re always in control of what’s optional.
Necessary
Necessary:
Keeps the website working, remembers your privacy choice, language and display preferences, and helps protect the site from bots. We also count visits without cookies or tracking. Always on.
Analytics:
Helps us understand how visitors find their way around our website, so we can improve it. With your permission we recognise you across visits, connect your visit to your account if you sign up, and keep anonymised session replays that show where visitors get stuck. Provided by PostHog, hosted in the EU (Frankfurt), and used only for InfraNest.
Marketing:
Remembers your referral, campaign and signup button for up to 90 days, lets our CRM (HubSpot) link your visit to your enquiry or signup, and lets our chat offer help on the page you are reading. Sets cookies. Recipients are listed in the privacy policy.
