Catch DNS issues before they cascade
Atatus checks your DNS answers and resolution time from nine locations every minute, against the nameserver you choose, and alerts you when a record or the speed is not what you expect.
- A
203.0.113.20 - A
203.0.113.21 - AAAA
2001:db8::20
- ✓response time is less than 100 ms11 ms
- ✓at least one record of type A is 203.0.113.20match
- ✓every available record of type AAAA contains 2001:db8match
Know when a record changes.
Assert on A, AAAA, CNAME, MX, TXT and NS answers. Change the rule and watch the verdict.
10 mail.example.commatches20 mx.other-host.netdoes not match
Sample answers · change the operator or value to see the check pass or fail
One server still has the old answer.
Point a check at a specific DNS server and port, or leave it empty for the default.
shop.example.com moved to 203.0.113.20. Pick a server to see what it answers.
- Domain
- shop.example.com
- DNS server
- ns2.example.com
- Port
- 53
- A
203.0.113.10
This nameserver still hands out the old address. A check pointed at it fails while the others pass.
One check per nameserver · sample data
Resolution time, run by run.
Every location, every minute, against the limit you set.
- 40 ms
- 26 ms
- 33 ms
- 57 ms
- 43 ms
- 48 ms
- 112 ms
- 114 ms
- 122 ms
Alerts go to email, Slack, PagerDuty, Microsoft Teams or a webhook once your retry and location rules are met.
See every check typeQuestions about DNS monitoring
Pricing, deployment, data and the agent. If something is missing, a person will answer it on a demo call.
DNS monitoring checks, over and over, that your domain resolves to the answers you expect and resolves quickly. Atatus DNS checks query your domain from the locations you pick, every minute by default, compare the records against your assertions and time each lookup. Because every service depends on DNS, a wrong or slow answer breaks many things at once.
A, AAAA, CNAME, MX, TXT and NS. For each type you can assert that every available record, or at least one record, is a value, contains a value, matches a regular expression or does not match it. You can also assert that the response time is less than a limit in milliseconds. The check fails, and can alert you, when an answer does not match.
Yes. Enter a DNS server, as a domain name or an IP address, and a port (53 by default), and the check asks that server directly. Leave it empty to use the default resolver. One check per nameserver shows you when one of them still hands out an old record.
Once a minute by default, from any of nine locations. You choose how many failures in a row a location needs before it counts as down, and at how many locations the check must fail before an alert goes out. Alerts go to email, Slack, Microsoft Teams, PagerDuty, OpsGenie, SMS through Twilio or a webhook.