Collect useful details when a DNS change is not working

Write down the full hostname, record type, old value if known, new value and the service you are connecting. For a mail issue, include the MX destination and affected address. For a website issue, state whether the root domain, www or a different subdomain fails.

1. Confirm the domain is in the correct client account.
2. Refresh DNS records and inspect the current value.
3. Open History & requests and note the last operation's status, time and reference.
4. Read any zone lock, quota, permission or provider error.
5. Run the propagation check for the exact hostname and type.
6. Compare the public nameservers with the DNS service you are editing.

For a website, include the URL and whether the browser shows a certificate error, wrong page, timeout or application error. For mail, include the test time, sender domain, recipient domain and returned delivery error. A message saying only that DNS is not working hides useful distinctions.

If you recently moved nameservers, enabled DNSSEC, changed a hosting package or edited an external DNS panel, mention it. Those actions can explain why the records displayed here differ from the answers visitors receive.

Do not send account passwords, API tokens, private keys, complete billing records or unrelated email content. A redacted screenshot can show the visible status, but include the error as text where possible. If you have a previous zone export, tell support that it is available and provide it through the secure ticket attachment option when relevant.

Keep the previous DNS service available during a planned migration and avoid repeatedly deleting/recreating the zone. If a change is still applying, wait for its final status or ask support to investigate the specific operation. Repeated retries can make the timeline harder to understand. When the records are confirmed correct but the service still fails, continue testing the web server, mailbox or application behind them.

• Check DNS propagation and find the source of an old answer
• Read DNS history and schedule a record change
• Fix missing DNS controls, read-only zones and limit messages
• Back up and restore DNS records