DNS Checker: Compare Remote Resolvers

Enter the exact public DNS name and select one record type. Keep both constant across comparisons. Looking up an A record at one hostname and an AAAA record at another does not provide a meaningful propagation comparison, even if the names belong to the same website.

Read the external-measurement consent and run the DNS checker once. The request asks for one probe in each of three regions. A provider can return fewer usable observations if a probe is unavailable or a test fails. The tool shows returned results instead of inventing a successful record for a missing region.

Compare each answer with its resolver, location and TTL. The city alone does not identify the recursive resolver’s cache or authoritative route. Different valid answers can arise from geographic routing, load distribution or deliberate DNS configuration; disagreement does not always mean a failed update.

Save the expected record and the observation time before checking again later. If a record was recently changed, consider the old TTL and which resolver cached it. Repeatedly changing the authoritative record while watching a few recursive responses can make the sequence harder to interpret.

A DNS checker that samples multiple locations asks a different question from a single DNS lookup. It helps compare how several recursive paths currently answer the same name and type. Those paths remain a sample: a probe’s resolver may forward elsewhere, and large public resolvers can serve distributed caches. This tool uses the resolver information actually returned by Globalping, not a geographic label alone, and retains the raw output. It does not provide a worldwide completion percentage because three observations cannot support that claim.

A DNS checker cannot determine what every visitor sees. Browser caches, local resolvers, enterprise networks and application caching introduce additional differences. Treat the result as evidence from the named paths at the shown time.

Some records intentionally vary. A content-delivery network can return different addresses to different resolvers without any configuration error. Compare the observed behavior with the intended policy before trying to make all rows identical.

A DNS propagation check does not test whether the application on the returned address works. An accurate record can point to a service with an unrelated TLS or HTTP problem. Use the relevant diagnostic task for that next question.

Suppose the three returned resolver samples contain two old values and one new value after a planned change. Preserve each value and TTL with its resolver before concluding anything. The pattern may reflect caches populated at different times, but it could also reflect deliberate DNS variation. Check the intended authoritative configuration and previous TTL rather than declaring propagation one-third complete. Three probes are not a random census of all users. The useful output is a small set of named observations that can guide the next authorized check.

Keep the question, input, observation time and source together. A bare address, percentage or status code is difficult to interpret later because it omits the connection and measurement context. When comparing two observations, note what changed between them: the target, network, VPN state, selected adapter, record type or remote origin. Change one relevant condition at a time when possible. That makes the comparison easier to explain without inventing a cause from one number.

Save only information you actually need. Network records can reveal infrastructure names and connection details, even when they do not contain a password. Remove unrelated identifiers before sharing a screenshot with another person. Never put private credentials in a domain field or publish an internal hostname as part of a public test. A copied result is a snapshot, not a promise that the same conditions still apply when someone reads it later.

Kepo is a Mac desktop-widget product for repeated checks and small workflows. A labeled troubleshooting note or a supported monitoring widget can keep the relevant context accessible while you work. The download link opens the product workflow; this article does not automatically install a configured diagnostic widget, transfer your network inputs or start a scheduled check. Confirm the actual widget’s capabilities before relying on it for ongoing observations.