I pushed two new features to the website recently.
NTP checks - run an ad-hoc check of a particular NTP server with results from a few randomly-ish chosen monitors. If an operator is trying to fix a firewall configuration, for example, it might be a quicker way to check if it’s working than trying to add a server (and you can do the check without trying to add the server to the pool…).
(working name, suggestions for the feature are welcome!)
The system counts how many times each server IP in the system is returned in response to a DNS request to the authoritative DNS servers and then calculates a percentage (displayed as a permyriad (per ten thousand) globally (all requests from all countries) and for each country (requests from that particular country).
I built this to prepare for the future improvements to how queries are distributed between servers so there’s a way to measure / observe if it’s working better.
This says that this server is included in ~5 1/10000th of IPv6/AAAA DNS replies (0.05%) globally and 1031 1/10000th of DNS queries from Austria (about 10%!)
This is all very new, but it’s been fun enough for me to look at that I thought it was worth sharing. Most of the DNS servers have been upgraded to include the logging data needed for this, but there are still some of the ~10 billion daily DNS queries that aren’t being logged with the answer data yet.
Another quirk about this is that it’s counting where users are querying from ignoring if they explicitly are requesting a different zone (say a user in the US doing a query for “ca.pool.ntp.org” will count as “us”).
I’m planning for eventually having the country zones go away as we’ve seen a meaningful amount of misuse or trouble from them and for basically everyone the automatic matching works well (if you disagree I’d love to hear about it).