Sorry, we don't support your browser.  Install a modern browser

DNS Monitor#20

?

A DNS monitor. Checks the returned IP of a query against an expected IP.

3 years ago
4
Changed the status to
Idea
3 years ago
1

I see the advantage of checking against expected IP for an A record, but also just notifying on IP/record change (additionally). Also checking a DNS server for response time and failures, which is another interpretation of the description “DNS Monitor”

2 years ago
?

good idea

2 years ago
1
P

For me MX checks to know if clients Email is operational. We manage the Email system but sometimes the client is still responcible (or worse another 3rd party) for the domain and the DNS settings and on many occasions they make changes without knowing properly what they are doing. Getting some warning that the MX records have been altered would be awesome. I know other companies do this, but I would prefer to keep all my monitoring in one place. Many thanks.

2 years ago

We just had a failure where our DNS was broken and our web site was unreachable to users but UptimeRobot didn’t fail connection to the HTTP(s) servers.

Guessing that it was using a cached IP address.

2 years ago

@Dean altough this isn’t the best solution, in the meantime one could make a keyword check on dns query via dns.google, e.g. like https://dns.google/resolve?name=example.org&type=A

2 years ago
3

I think there are different scenarios that a DNS test should cover:

change from a specified value
any change, e.g. TTL, or change of the resolved value

But the URL method mentioned by @Felix to test DNS records is also very creative way to tacle this.

@Dean Keep in mind that the TTL may be the issue here as those cached records will continue to resolve, while the TTL is still valid. e.g. 24 hour TTL. The more important test here that you are describing is the DNS server is reachable, not the DNS records. If you can’t device a DNS reachability test, you could alternatively set a dummy A record with 5 second TTL. This might solve, if you cannot test your DNS server is reachable.

a year ago

Good idea 👍

10 months ago
A

Unfortunately, it is not possible to check a DNS server correctly with Uptime Robot. Simply querying port 53 is not enough. I would find this an important function, as functioning DNS servers have an important function for the Internet.

7 months ago
?

mum, two years later – would be valuable tho

6 months ago