ClueDNS: find the owner before the next DNS change
Suppose a site stops resolving after a nameserver change. The records in the DNS host’s panel look correct, so the next instinct is to edit something and wait. But the answer your users see may come from a registrar, a resolver cache, a CDN or a mail provider that nobody has checked, and editing the visible record will not fix a problem that lives elsewhere.
Several parties shape one domain
A domain’s behavior depends on the registrant, the registrar, the DNS host, the resolvers your users happen to use, and whatever CDN, web host or email provider sits behind the name. One lookup from one laptop shows what one resolver returned at one moment, not which system produced that answer or who is allowed to change it.
ClueDNS exists to close that gap. It is a knowledge-first DNS resource, owned and operated by VMCSoft Digital, built around a plain order of work: understand the control plane, inspect without changing anything, interpret the evidence, then change with a plan and verify again. The site’s own summary is “evidence before action.”
What it offers, and what it leaves alone
The site is organized into Learn, Fix, Playbooks and Labs. Learn separates the roles in the control plane. Fix starts from a symptom, such as NXDOMAIN or a website that works while mail fails, and walks through read-only inspection. Playbooks cover changes with preflight checks, stop conditions, verification and a tested rollback path. The methodology labels each conclusion by the strength of its evidence, from authoritative sources down to editorial recommendation, and names who owns the next change. One resolver’s answer is never presented as global DNS state.
Live checks stay separate. ClueDNS links to focused tools where they are relevant, and a check runs only when you choose to open one.
ClueDNS is not a registrar, DNS host, CDN or monitoring product, and it does not promise that following a playbook will prevent downtime. It is permanently free, with no account and no feature paywall, as the about page states.
Where it sits in the portfolio
Within VMCSoft Digital, ClueDNS answers “who controls this?” rather than “is this up?” Availability belongs to monitoring tools and implementation to whoever operates the zone. ClueDNS covers the step between: turning a symptom into evidence and an owner before anyone edits a record.
When troubleshooting, start in Fix with the symptom you actually see. When preparing a change, start in Playbooks and run the preflight checks. Either way, leave the record editor closed until you know whose answer you are looking at.