New: temperature, fans, power supplies and SSD health per server. View hardware health

Try it free
DNS monitoring in the PeakNode portal: header “No DNS changes in the last 7 days” with three active monitors and eleven DNS records, below three domains with the number of checks and changes.

The DNS records of a domain determine which server hosts your website and where your email goes. If someone changes them, by mistake or on purpose, you will not notice on the server itself. PeakNode reads the records at fixed intervals and reports what has been added, removed or changed.

Screenshot from the portal with sample data (German interface).

What is DNS monitoring?

DNS monitoring with PeakNode watches the DNS records of a domain, that is, the entries that determine where the domain’s website and email lead, and reports every change. For each monitor you choose the record types: A, AAAA, CNAME, MX, NS, TXT, CAA and SOA. PeakNode queries them at the configured interval, compares the result with the stored state and notifies the selected channels. Every change is then recorded in the monitor’s log.

What a DNS monitor tells you

The monitor tells you that a record has changed, and how.

Eight record types to choose from

For each monitor you choose which types are watched: A and AAAA for the addresses, CNAME, MX for mail, NS for the nameservers, TXT, CAA for the permitted certificate authorities, and SOA. SRV and PTR records are not included.

The order of the records does not matter

Several records of one type do not always come back in the same order. PeakNode therefore compares the records themselves: what is new counts as added, what is missing as removed. The TTL, that is, how long a record is valid, is not part of the comparison.

The notification says what changed

The notification states the type, the kind of change and the value, and for SOA the old and the new state. It goes to the channels you selected on the monitor. The webhook channel only transmits the monitor, the domain and the link to the details.

No false alarm when the query fails

If the query for a type fails, for example with SERVFAIL or a timeout, that type is not compared and its last state is kept. If all types fail, PeakNode stores nothing and queries again after at most 5 minutes.

Log of changes

Under “DNS changes”, every detected change is listed with its date, for the retention period of your plan. The detail page shows the current state per type, the number of checks, the total number of changes and the time of the last change. Checks without a change are counted, but not logged individually.

The initial state does not trigger a notification

The first check takes over the current state of the domain without notifying. The same applies when you add another record type later.

What the notification looks like after a change

Notification for example.org

Record typeChangeValue
ARemoved203.0.113.10
AAdded203.0.113.24
MXAddedPriority 10, mail.example.org
TXTRemovedv=spf1 mx -all
SOAChangedOld: ns1.example.org hostmaster.example.org 2026111001
New: ns1.example.org hostmaster.example.org 2026111101

Example, labels as in the portal. A changed A record appears as one removed and one added record.

Which records PeakNode watches

What each record defines and what an unexpected change can mean.

Record typeWhat the record definesWhat a change can mean
A and AAAAIPv4 and IPv6 address of a nameThe service has moved, or the name points to someone else’s server
CNAMEAlias to another nameThe service points to a different target, for example after a change of provider
MXMail servers of the domain with priorityMail is delivered to a different server
NSAuthoritative nameserversThe zone is hosted by a different DNS provider
TXTFree text, including SPF and verificationsChanged sender rules, a new or removed verification
CAACertificate authorities allowed to issue certificates for the domainRenewing a certificate can fail if the authority in use is missing
SOAZone data with serial numberThe zone has been edited. If you select SOA, you learn about every change of the serial number

The values compared per type are: for A the address, for MX the target and priority, for CAA the flags, tag and value, for SOA all fields including the serial number. Queries go through the portal’s resolver, not to each authoritative nameserver individually and not from several locations.

Set up in three steps

All you need is the name of the domain.

  1. Create a DNS monitor

    Under “DNS monitors”, go to “Create DNS monitor” and enter the domain, for example example.org. A subdomain such as api.example.org is a separate target with its own monitor.

  2. Choose types and interval

    Set the check interval and, under “Advanced settings” in “DNS types”, choose which records must not change unnoticed. By default all eight types are ticked. If you want fewer notifications, start with A, AAAA, MX and NS for a production domain.

  3. Set channels

    Select notification channels and save.

Frequently asked
questions about DNS monitoring

Continue to:

What is DNS monitoring?

DNS monitoring watches the DNS records of a domain and reports when one of them changes. PeakNode queries the selected record types at fixed intervals and compares them with the last stored state. The types A, AAAA, CNAME, MX, NS, TXT, CAA and SOA are monitored, SRV and PTR records are not.

How quickly do I learn about a DNS change?

Usually with the next check. You can choose 5, 10 and 30 minutes, 1, 6 and 12 hours, and 1 day, depending on the plan. PeakNode queries through a resolver, a service that answers DNS queries and may cache responses: detection can therefore take longer until the validity period of the old record has expired. A change that is reverted between two checks is not seen by the monitor.

Does PeakNode detect DNS hijacking, that is, a redirected domain?

PeakNode detects that a record has changed and states the removed and the added value. Whether the change was intended is for you to decide. The monitor queries through the portal’s resolver: tampering that only affects individual networks or resolvers is not visible to it.

Do I get an alert when the nameserver does not respond?

No. A DNS monitor reports changes, not outages. If the query fails, the last state stays and no notification goes out. Whether a service is reachable under its name is checked by an uptime monitor: if the hostname cannot be resolved, its check fails.

Why does the monitor report two changes for a changed A record?

Because PeakNode compares records as a set. The old address is missing, hence “Removed”, and the new one has been added, hence “Added”. Only the SOA record, which exists once per zone, appears as “Changed” with the old and new state.

Can I monitor internal DNS zones?

Not in the cloud edition: PeakNode does not query internal names. If, however, a public name suddenly points to a private address, that is a change that gets reported. The on-premises edition also queries internal names.

Does someone have to acknowledge a DNS notification, and is there an escalation?

No. A DNS change is a one-off event and not an ongoing outage. That is why there is no incident, no reminder and no all-clear for it. The notification goes to the selected channels once, and the change is then recorded in the monitor’s log.

How can I check my DNS server?

You check individual records with dig or nslookup directly against your nameserver. On an ongoing basis, a DNS monitor in PeakNode watches whether the records of your domain change. Whether the nameserver itself is reachable is checked by a port monitor on TCP port 53, as long as the server is publicly reachable and accepts queries over TCP, see uptime monitoring.

Put your most important domain under watch

Create an account, enter the domain, choose record types. The first check takes over the current state, later changes are reported.