Help / Monitors
DNS monitor
A DNS monitor looks up one DNS record from our checking cities. It can tell you when the lookup fails, when the answer is not what you expect, and when the answer changes.
What you need first
- The name to look up, for example
example.comorwww.example.com. - The record type you care about. You can choose A, AAAA, CNAME, MX, TXT, NS, SOA or CAA.
- Optionally, the value the answer should contain, such as your server's IP address.
Set it up
- Open Monitors and press Add monitor.
- Choose DNS record.
- In Name to look up, type the name without
https://. - In Record type, pick the type.
- Optionally, fill in Answer must contain. For an A record this is usually an IP address, for example
203.0.113.5. - Optionally, fill in Ask this DNS server with the IP address of one DNS server, for example
1.1.1.1or your own name server. Leave it empty to use each checking city's normal resolver. - Leave Alert when the answer changes ticked if you want to hear about changes (see below).
- Give it a Friendly name, choose Check every, and press Start monitoring.
When it counts as down
A check fails when the lookup gives an error, for example when the name does not exist or the server does not answer in time. If you filled in Answer must contain, the check also fails when none of the answers contains that text. The match ignores upper and lower case and a trailing dot, and it looks for your text anywhere in the answer. So mail.example.com matches an MX answer of 10 mail.example.com.
With the default settings, two cities must fail twice in a row before the monitor is down and you get a down alert. You can change this under More settings, as for other monitors. See How checks work.
Alerts when the answer changes
With Alert when the answer changes ticked, HonkWatch remembers the answer most cities get back. When that answer changes, you get one alert that lists the old records, the new records and the cities that saw the new answer.
- The first answer after you save is the starting point. Nothing is compared until then.
- A change only counts once more than half of the reporting cities have seen the same new answer on two checks in a row. A record that is still spreading, or one stale resolver, stays quiet.
- You get at most one change alert every 6 hours for each monitor. Services that rotate their addresses all day would otherwise send a stream of them.
- A change is not downtime. It opens no incident and does not affect your uptime figures.
- Change alerts go to the channels that have Down ticked on the Alerts page, except PagerDuty.
- No change alert is sent during a maintenance window.
- If you change the name, record type or DNS server, the next answer becomes the new starting point.
Names served through a CDN or round-robin DNS often give different answers from different places. If change alerts are noisy, untick the box and use Answer must contain instead.
Send a test
Open Alerts and press Send test on each channel. Then open the monitor. After the first round, By location shows the answer each city got and how long the lookup took. The Settings card shows the record and the expected answer.
When it does not work
- An error that starts "Expected". The lookup worked, but no answer contained your text. The error shows what came back. Check for a typing mistake, or a record you changed recently.
- An error that starts "NXDOMAIN" or "NoAnswer". NXDOMAIN means the name does not exist. NoAnswer means the name exists but has no record of the type you picked. Check the spelling, and pick the record type the name really has.
- You set a DNS server and every check fails. The server must be a public IP address that answers queries from the internet. A host name gives "DNS server must be an IP address", and a private address such as
10.0.0.2is not allowed either. - An answer shows as "(private address)". The record points to a private address. It is hidden on purpose.
Still stuck? Email [email protected] and say which guide you were following.