To monitor DNS record changes, record a baseline of each domain's important records (nameservers, A and AAAA, MX, and the TXT records for SPF, DKIM and DMARC), check them again on a schedule, and get an alert whenever something differs from the baseline. You can do this by hand on Windows with PowerShell, but for more than a few domains an automated monitor is far more reliable.
DNS changes are one of the earliest warning signs of trouble. A changed nameserver can mean a hijack, an expired domain parked by its registrar, or a well-meaning colleague who moved something without telling anyone. Here is what to watch and how to set it up.
Which DNS records to monitor
Not every record needs watching, and too many alerts get ignored. Focus on the records that would break something important if they changed:
| Record | What it controls | A surprise change could mean |
|---|---|---|
| NS (nameservers) | Which DNS provider answers for the whole domain | Hijack, expiry parking, or an unannounced move. The most important record to watch. |
| A and AAAA | The IP addresses your website points to | Site moved, compromised DNS account, or a hosting change. |
| MX | Where incoming email is delivered | Email being intercepted or lost. |
| TXT (SPF, DMARC) | Which servers may send mail as you, and what receivers do with failures | Mail delivery problems or weakened spoofing protection. |
| CNAME on key hosts | Aliases such as www, shop or mail | A service pointed somewhere unexpected. |
| CAA | Which certificate authorities may issue certificates | Certificate renewals failing, or issuance opened up to others. |
If you need a refresher on what each record type does, see DNS record types explained.
Step 1: Take a baseline on Windows
Windows PowerShell includes Resolve-DnsName, which is clearer than the older nslookup. Create a folder such as C:\dns, open PowerShell and run one command per record type, saving the results:
Resolve-DnsName example.com -Type NS | Out-File C:\dns\example-ns.txtResolve-DnsName example.com -Type A | Out-File C:\dns\example-a.txtResolve-DnsName example.com -Type MX | Out-File C:\dns\example-mx.txtResolve-DnsName example.com -Type TXT | Out-File C:\dns\example-txt.txtResolve-DnsName _dmarc.example.com -Type TXT | Out-File C:\dns\example-dmarc.txt
Also note the nameservers shown in an RDAP or WHOIS lookup. Those come from the registry, which makes them the authoritative answer to "who controls this domain's DNS".
Your PC's resolver may return cached answers. To see exactly what the domain's own DNS server says, add -Server followed by one of the domain's nameservers, for example -Server ns1.yourdnsprovider.com.
Step 2: Compare on a schedule
To check for changes, run the same commands into a new set of files and compare them. In PowerShell:
Compare-Object (Get-Content C:\dns\example-mx.txt) (Get-Content C:\dns\example-mx-new.txt)
No output means no change. Any lines that appear are the differences. Ignore the TTL column if it varies, since cached answers count TTLs down.
You could put these commands in a script and run it daily with Task Scheduler. It works, but it takes upkeep: every new domain needs new lines, legitimate changes need a new baseline, and you still have to read the output. This is where most manual monitoring quietly stops happening.
Registry changes vs zone changes
DNS information lives in two places, and changes in each mean different things:
- At the registry: the list of nameservers (and DNSSEC DS records, if you use DNSSEC) is stored with the registry and changed through your registrar account. A change here moves control of the entire domain to another DNS provider. It shows up in RDAP and WHOIS lookups.
- In the zone: A, MX, TXT, CNAME and other records live in the zone at your DNS provider, which may be your registrar, your host or a separate DNS service. Changes here affect individual services such as the website or email.
An unexpected registry-level change is the more serious of the two, because whoever controls the nameservers controls every record. It usually means someone used your registrar account, or the registrar changed the nameservers itself after the domain expired. A zone change is more often a hosting or developer change, though a compromised DNS or hosting login can cause one too. Monitoring both tells you which account to check first.
How often to check
- Daily is enough for most business domains and portfolios.
- More often for high-value domains, e-commerce sites, and any domain during a hosting move or registrar transfer.
- Immediately after any planned change, to confirm the change you made is the one that took effect.
What to do when a DNS change alert fires
- Ask whether it was planned. Check with colleagues, your web developer or hosting provider. Most changes are legitimate.
- Check the domain status and expiry. If the nameservers changed to a registrar's parking servers, the domain may have expired. See what happens when a domain expires.
- Check the registrar account. Log in and look for recent activity, changed contact details or a pending transfer.
- If it was not you, act fast. Change the registrar password, turn on two-factor authentication, restore the correct records and contact the registrar. Our guide to the signs your domain has been hijacked covers the full response.
- Update your baseline once you are satisfied the new values are correct.
Beyond records: status and website checks
DNS monitoring catches a lot, but two related checks fill the gaps. Watching the domain's status codes shows when a lock is removed or a domain enters redemption. Checking that the website responds catches hosting outages where the DNS is fine but the server is not. Together, these three checks cover most of the ways a domain-dependent service fails.
Automated monitoring with Names Organizer
Names Organizer is a Windows domain manager that includes DNS, nameserver and website monitoring. It keeps each domain's nameservers and DNS records on file, and warns you if they change unexpectedly, if a domain's status changes, or if a website stops responding. Those are the early signs of a hijack, a billing problem or a hosting outage, delivered as a desktop notification or email instead of a customer complaint.
When you refresh, you can see what changed since last time for each domain. For audits or before moving hosts, the DNS and nameservers report lists the records per domain and can be printed or saved as PDF or text, which also gives you a written baseline to restore from if something goes wrong. Names Organizer works across every registrar and DNS provider, because it reads the public DNS rather than logging into each account.
Frequently asked questions
Which DNS records are most important to monitor?
Nameservers first, because they control everything else. Then A and AAAA records for your website, MX records for email, and TXT records that hold SPF, DKIM and DMARC.
How often should DNS be checked?
Daily is enough for most portfolios. Busy agencies and high-value domains benefit from more frequent checks, especially around a hosting move.
Will I notice a DNS change without monitoring?
Often not until something breaks. A changed MX record can quietly redirect email for days before anyone realizes messages are missing.
