Find which DNS service actually answers for your website and mail

• Registration and parent delegation: the registrar submits the nameservers that the parent zone publishes for your domain.
• Authoritative zone: the delegated DNS servers hold the records used to answer queries for that zone.
• Recursive resolver: the user's network or selected DNS service looks up those records and can cache earlier answers.
• Application destination: the returned address or mail route leads to the website, proxy or email service.

1. Write down the exact hostname and record type that are wrong, such as www.example.com A or example.com MX.
2. Check the live parent delegation using a trace or suitable DNS diagnostic tool.
3. Query the delegated authoritative nameservers directly for that same name and type.
4. Compare their response with the record in the DNS account you intended to edit.
5. If the hostname is an alias, follow its target. If it is beneath a delegated subdomain, identify the child zone's authoritative service.

The registrar, hosting panel and an external DNS provider can each contain a stored zone. Only the zone reached by the live delegation affects ordinary public queries, except for deliberately configured split DNS or other specialised arrangements. Editing an inactive copy does not update the active provider.

In Domain Nexus, check the zone's assigned provider and operation history, then verify its public authority. An API sync or successful record save does not itself change the parent delegation. Nameserver and record changes must be planned together when moving DNS.

Compare the recursive answer and its remaining TTL, then check the destination service. A reverse proxy, cached page, application redirect or invalid certificate can produce the symptom after DNS is already correct. Give support the exact hostname, query results and observed error so the next investigation starts at the failing layer.

• Query authoritative nameservers directly when diagnosing DNS
• Trace a DNS delegation from the root to the final authoritative zone
• Why a newly created DNS name can remain absent in a resolver cache
• Choose hosting nameservers or DNS management for your domain

• IETF RFC 1034: Domain names, concepts and facilities
• IETF RFC 1035: Domain names implementation and specification