Insights:7 Most Common Mistakes with Domains and DNS
Pitfall 1: Only Changed One NS
Impact: Intermittent DNS resolution — results vary by region, making them hard to reproduce during troubleshooting.
Cause: Registrars usually require two or more NS records; changing only one leaves the old provider's servers still responding.
Check: Run dig NS domain to inspect the returned list, confirm all entries point to the new provider, and verify each NS resolves correctly.
Pitfall 2: Didn't Lower TTL Before Changing IP
Impact: Old IP cache hasn't expired yet, so some users keep hitting the old server; if the old server is already shut down, those visitors see a blank page or 502 error.
Cause: The TTL remained at 24 hours or more, leading to the assumption that the record update takes effect immediately.
Check: Lower the TTL at least one full TTL cycle before switching servers; after updating, watch the old server's logs and confirm traffic has stopped before decommissioning it.
Pitfall 3: Configured Only www, Not the Root Domain
Impact: Visitors who type the address without www can't reach the site, or they're served a different website instead.
Cause: An A or CNAME record was set up for www only, leaving the root domain without any record.
Check: Access both the root domain and www; confirm one does a 301 redirect to the other; ensure both with and without a trailing slash resolve to the same address.
Pitfall 4: Placing a CNAME Directly on the Root Domain
Impact: Some resolvers reject it, causing conflicts with mail and verification records, leading to unstable DNS behavior.
Cause: By DNS standards, a CNAME is not appropriate at the root (apex) domain; while some providers work around this with ALIAS/ANAME, support isn't universal.
Check: Use A/AAAA for the root domain; if your provider supports ALIAS, follow their docs; don't force a plain CNAME onto the apex.
Pitfall 5: Conflicting MX and SPF records
Impact: Can receive but not send mail, or messages land in spam; in severe cases the entire domain is flagged as forged.
Cause: Switched email providers but left old MX records; multiple SPF TXT records coexist; DKIM not configured.
Check: Keep only the current provider's MX records; retain a single SPF record; configure DKIM per provider instructions; set DMARC to monitoring first, then tighten.
Pitfall 6: Certificate covers only one domain
Impact: The main domain works fine, but www or subdomains show certificate errors; users see the warning and leave immediately.
Cause: Only a single-domain certificate was issued, or the certificate chain is incomplete.
Check: Visit the main domain, www, and all common subdomains; confirm the cert chain is complete and set expiry reminders; ensure HTTP redirects to HTTPS via 301.
Pitfall 7: No ownership of expiration and accounts
Impact: Domain expires and DNS stops resolving, possibly getting snapped up by others; renewal alerts go to an unchecked inbox.
Cause: Domain is registered under a former employee's account; renewal notices are sent only to a personal email; no second person has access to act.
Check: Register the domain under an organizational account; enable two-factor authentication; record expiration dates well in advance; grant at least two people operational access; rotate passwords after transfer.
Troubleshooting order when issues arise
Start with NS and A/AAAA, then check TTL and cache, and finally inspect certificates and email. Don't jump straight into changing records—first capture the current resolution output so you have a reference for rollback.
Related reading: