---
title: "DNS monitoring and change history"
description: "Time machine records every DNS change with the record before and after, including changes made directly at the provider. Revert any of them in one click."
canonical_url: "https://dnsense.io/dns-monitoring"
---

> Index of every page on this site: [llms.txt](https://dnsense.io/llms.txt)

<key-visual-subpage ctaHref="https://app.dnsense.io/" ctaIcon="ArrowUpRight" ctaLabel="Start for free" description="Most outages start with one wrong value, not a big migration. Time machine records every change, also the ones somebody made straight in the provider panel, and puts it back in one click." highlight="even outside DNSense" imageAlt="Zone with the Time machine panel open" imageUrl="feature-monitoring-hero.webp" title="Know what changed, even outside DNSense">



</key-visual-subpage>

<feature-rows :rows="[{"title":"The full record, before and after","titleIcon":"Clock2","description":"Every entry holds the record as it was and as it became, not a line of text describing it. Search a zone's history by name, type or content to find the one change that matters.","imageUrl":"feature-monitoring-history.webp","imageAlt":"Time machine with the before and after values of a change","bullets":["The person behind every change, or a clear mark when it happened outside DNSense","One history per zone, whichever provider hosts it","Revert a created, edited or deleted record with one click"]},{"title":"Changes made at the provider are caught too","titleIcon":"Radar","description":"A colleague logs in at Cloudflare and edits the A record directly. DNSense compares your zones with what the provider serves, so that change still lands in Time machine, marked as made outside DNSense.","imageUrl":"feature-monitoring-outside.webp","imageAlt":"Notification of an A record changed outside DNSense, with old and new value","bullets":["Zones are rechecked in the background, no action needed","Outside changes can be reverted like any other change","The team gets a notification with the old and new value"]},{"title":"A refusal in the provider's own words","titleIcon":"ShieldCheck","description":"Provider APIs fail in their own way. DNSense queues each change, follows it through and tells you the moment one is refused, with the reason the provider gave.","imageUrl":"feature-monitoring-failed.webp","imageAlt":"Recent activity with a change the provider refused and its error message","bullets":["No generic \"something went wrong\", the provider's message as it was returned","The zone it concerns one click away","A change that stalls halfway is flagged instead of reported as done"]}]" highlight="what it was before" label="DNS monitoring" title="Who changed it, when, and what it was before">



</feature-rows>

<faq :faqs="[{"question":"How long is my DNS history kept?","answer":"Time machine keeps every change made inside your zones with no cut-off date, so you can look back at an old change and revert it whenever you need to."},{"question":"Does DNSense notice changes made directly at my provider?","answer":"Yes. DNSense rechecks your zones against the provider in the background. A change made outside DNSense shows up in Time machine and in your notifications, and you can revert it there."},{"question":"Is the zone history the same as the audit log?","answer":"No. The zone history holds DNS record changes with the record before and after, ready to revert. The audit log covers every action in the platform, including logins, roles and connections."},{"question":"Which plans include DNS monitoring?","answer":"All of them. Nothing in DNSense is locked behind a plan, so monitoring is there from your first domain on the free tier."}]" decorativeShape="bottom-left" label="Questions" title="Frequently asked questions about DNS monitoring">



</faq>

## Sitemap

See the full [sitemap](https://dnsense.io/sitemap.md) for all pages.