Domain check

Name server health monitoring

DoubleCheck asks every name server of your domain for the zone itself, and alerts you when one does not answer or is out of step with the others.

The problem

A domain has two or more name servers so that it keeps working when one fails. But when one of them is down, or stops being updated, nobody sees it: the others keep answering.

The result is a domain that works for some visitors and not for others, or that returns old records. That kind of problem comes and goes, and is hard to reproduce.

Why it matters

A name server that does not answer takes away your redundancy, and a part of the lookups becomes slow or fails.

A name server that is not authoritative for the zone (a lame delegation) or that gives an older SOA serial means the zone is not kept in step, for example because a zone transfer failed.

How to check it manually

Ask each name server for the SOA of the zone with dig, and compare the serials:

dig +short NS example.com
dig +short SOA example.com @ns1.example.com
dig +short SOA example.com @ns2.example.com

How DoubleCheck checks it

DoubleCheck finds the name servers of the zone, and asks each one directly. A server that does not answer, or says it is not the authority, is an error and is named in the message. Different SOA serials, or a single name server, give a warning.

Only public IPv4 addresses are asked. A name server whose address points to an internal network is reported as a problem and not contacted.

example.com 1 warning
Domain checks · 8 checks · once a day
SPF-all · 4 of 10 lookups
DKIM selector12048 bits
DMARCp=none · 1 report address
MX2 of 2 expected
NS2 of 2 expected
Name servers2 answer, same serial
Blacklistclean on 20 lists
Domain expiry287 days left
90 days agoOK Warning Not checked yettoday
Sample data. The domain checks of one domain, each with its last result and one square per day for the last 90 days. A new check starts grey.
Measures
The NS records of the domain, and then an SOA query to every name server itself. DoubleCheck reads whether each server answers, whether it is authoritative for the zone, and which SOA serial it gives.
Runs
Once a day. The interval is the same for every domain check: what it reads rarely changes.
Status
  • OK when every name server answers as an authority for the zone and they all give the same SOA serial.
  • Warning when the name servers give different SOA serials, or the domain has only one name server, unless you accepted that.
  • Error when a name server does not answer, is not authoritative for the zone, or has no public IPv4 address.
  • Error when no name servers are found for the domain.
  • Unknown, and no alert, when the DNS resolver does not answer.
Options
  • Name servers with a different serial number: a warning by default. Choose "accept" when your DNS provider does not keep them in step.
  • Only one name server: a warning by default. Choose "accept" to allow it.

All of it in one report

Want to see this next to the rest of the mail setup of a domain? The e-mail health report reads MX, SPF, DKIM, DMARC, blacklists, name servers and the domain registration at once and gives you a PDF with findings and advice, for €0.20.

FAQ

Frequently asked questions

Is a different SOA serial always a problem?

Right after a change it is normal for a moment. That is why such a result is a warning. Some DNS providers do not keep serials in step on purpose. If that gives you a permanent warning, accept different serials in the options of the check.

Why only IPv4?

A monitoring server without IPv6 would otherwise report healthy name servers as down. The check asks the IPv4 address of each name server.

Which domain do I enter?

The domain, for example example.com. For a name below a zone, such as www.example.com, DoubleCheck goes up to the zone that has the name servers.

Get started

Start monitoring with DoubleCheck

Start with €5 of free credit, no credit card required. Alerts by email, SMS, Slack, Microsoft Teams or Discord.

Start monitoring