Search... ⌘ K
Get Started Contact Sales

Troubleshoot Email or Subdomains After Delegation Changes

Delegation can be correct at the registry while mail or a hostname still fails. Use the checks below to confirm that public resolvers reach DNSimple for your zone and that the records you expect exist on the authoritative side.

Table of Contents

Before you start

Read How DNS Caching and TTL Affect Delegation and Record Changes so resolver caching does not look like a misconfiguration. Flush local cache if needed (Check DNS Cache).

Confirm delegation

Verify name servers in DNS
  1. Run dig NS yourdomain.com +short (replace yourdomain.com).
  2. Compare the result to DNSimple name servers. All four should appear and no unexpected third-party NS should remain unless you intentionally use Secondary DNS.
  3. If delegation is wrong, follow Pointing a Domain to DNSimple and wait for caches to expire, then retest.

Note

dig NS example.com +short uses the resolver you query. Results can be cached, so if you changed delegation recently, you may still see old name servers until the previous delegation TTL expires. For background, see How DNS Caching and TTL Affect Delegation and Record Changes.

Broader checks: Troubleshoot DNSimple Name Servers and Troubleshoot Domain Resolution Issues.

Email still undeliverable

  1. Run dig MX yourdomain.com +short at a public resolver (for example dig @8.8.8.8 MX yourdomain.com +short).
  2. Confirm the MX targets resolve (A/AAAA) and match what your mail host expects.
  3. In DNSimple, open the zone and confirm MX records (and any required SPF, DKIM, or DMARC TXT records) exist on the apex domain that receives mail.
  4. If you send from the domain, review Email DNS Records Quick Reference for missing authentication records.

If delegation was wrong until recently, remote senders may still retry against old paths; combine DNS fixes with How DNS Caching and TTL Affect Delegation and Record Changes.

Subdomain still fails

Trace authority for the hostname
  1. Query the specific name: dig A full.hostname.yourdomain.com +trace or dig CNAME full.hostname.yourdomain.com +trace depending on record type.
  2. Confirm which zone is authoritative. If a parent zone delegates the subdomain with NS records, those child name servers must hold the records you expect.
  3. If the subdomain should live on DNSimple, ensure no stale NS at the parent points elsewhere.
  4. For resolution errors after edits, see Troubleshoot Record Resolution Issues.

Have more questions?

If you are stuck after these checks, contact support with dig output for NS and the failing record type, and we will be happy to help.