DNS record check Beta
Type dns: resolve a name and check the answer. It catches the outages that happen before anyone reaches your server, such as a record that was edited by mistake or a zone that expired.
There is no separate endpoint for this: it is the ordinary create a monitor call with type set to "dns". The same settings apply when you update a monitor with PATCH /api/v1/monitors/{id}.
Every type shares the same interval, retries, alerting, maintenance, results and reports. Only the settings below differ. See Check types for how the nine types compare.
Up or down
- Up when the name resolves and there is at least one record of the type you asked for.
- With
dnsExpected, one of the answers must contain that text, ignoring case and a trailing dot. Otherwise: The A record doesn't match, with the answers that did come back. - A name with no such record gives No A record for that name, and a name that doesn't exist gives That name doesn't exist.
- The response time is how long the lookup took.
Record types
A, AAAA, CNAME, MX, TXT, NS and SOA. Answers are flattened to plain text before dnsExpected is compared: MX matches the mail host, TXT the joined string, and SOA the primary nameserver.
Settings that apply
| Setting | Notes |
|---|---|
url required | The name to resolve, for example example.com. Not a URL. |
dnsRecordType | One of the seven above. Default A. |
dnsExpected | The answer must contain this. Up to 500 characters. Leave it empty to check only that the record exists. |
dnsNameserver | Ask this server instead of the default resolver. Up to 255 characters, and it must be a public address. Use it to check that your own nameservers agree. |
timeoutSeconds | How long to wait for the answer. |
Create one
Check that the mail records still point at your provider:
Check one nameserver directly, so you notice when it drifts from the others:
Related
- Mail server checks: check the server those records point at
- Check types: hosts, ports and duplicates