FeaturesHow it worksUse casesPricingHelpLog inSign up
FAQ

Common DNSReach questions

Short answers to the questions that come up most often.

Does DNSReach count every resolver IP separately?

No. Multiple IPv4 or IPv6 endpoints can belong to one logical resolver. That resolver counts once in consensus.

Are public resolvers geographic probes?

No. Anycast and public resolvers are not presented as if they prove a query came from one city. DNSReach geographic nodes are separate.

What does an expected value do?

It lets DNSReach compare answers with the DNS value you expect during a change and report propagation progress.

Does a timeout mean the DNS record is wrong?

No. A timeout means that source did not answer in time. It is kept separate from a valid DNS answer that differs.

Can I check PTR records?

Yes. PTR checks accept IPv4 and IPv6 addresses.

Why can resolvers return different answers?

DNS caches refresh at different times. DNSReach separates a different valid answer from a timeout, refusal or DNS error so you can see what is actually happening.

What is authoritative DNS?

These are the nameservers responsible for the DNS zone. DNSReach checks them separately so their answers do not distort public resolver consensus.

What are geographic nodes?

DNSReach nodes run checks from real installed locations. They are shown separately from global anycast resolvers because the two types of evidence answer different questions.

Does DNSReach support DNSSEC?

DNSSEC evidence is being expanded. Where DNSSEC information is available, DNSReach keeps validation evidence separate from ordinary record comparison.

Can I automate checks?

Eligible accounts can use authorised API or MCP access. Scraping the public website or bypassing plan limits is not permitted.

What happens when a resolver has a known problem?

DNSReach can hold an unhealthy endpoint out of public comparison while continuing health tests. Healthy endpoints for the same logical resolver can continue to work.

Still have a DNS question?

Run a check first, or contact technical support if you need help understanding the evidence.

Run a DNS check