To fix DNS resolution issues, verify your domain's nameservers point to the DNS host where your A/AAAA records live, confirm those records point to your web server's current IP, remove stale or conflicting records, and wait for TTL-based propagation. Re-scan once global resolvers return the correct address.
A DNS resolution issue means the domain name does not map to a reachable IP address — visitors may see errors, and scanners cannot complete checks. The fix is almost always correcting A/AAAA records, nameserver delegation, or propagation after a migration.
Check your website
See how your site handles how to fix dns resolution issues — free, no account needed.
Business impact
If DNS is wrong, your site is effectively offline even when your server is running. Email can break too if MX records are affected. For any business that depends on its website, DNS resolution is the first thing to verify in any outage or post-migration checklist.
Why this happens
Scanners report "DNS Resolution Issue" when no A records resolve for the scanned hostname. Causes include: nameservers still pointing at an old DNS host after a move; A record pointing at a decommissioned IP; typo in the record; registrar hold or expired domain; or propagation in progress after a recent change. AAAA issues alone may not trigger this finding but still affect IPv6-only clients.
How to confirm the issue
Manually: run nslookup yourdomain.com or dig yourdomain.com A. No answer or wrong IP confirms the problem. Compare with your hosting panel's expected IP.
With Plexa Trust: look for "DNS Resolution Issue" in scan results. After fixing records, re-scan — the finding should clear once resolvers worldwide see the correct A record.
Step-by-step fix
Confirm the domain is registered and not expired or on hold.
Identify where DNS is managed (registrar, Cloudflare, Route 53, host panel).
Check nameservers at the registrar match the DNS host that holds your A record.
Set or correct the A record to your web server's current public IPv4 address.
Remove duplicate or conflicting A records; add AAAA if you support IPv6.
Lower TTL before changes if you need faster propagation; wait for cache expiry.
Test from multiple networks or use a global DNS checker, then re-scan.
Platform-specific fixes
Cloudflare
DNS → ensure an A record exists for @ pointing to your origin server IP.
If the site is proxied (orange cloud), Cloudflare's anycast answers — but origin must still be valid.
Check nameservers at your registrar are the two Cloudflare NS names assigned to your zone.
GoDaddy / Namecheap (DNS at registrar)
DNS management → A record, Host @, Points to your server IP.
Remove old A records pointing at previous hosting.
Nameservers should be the registrar's defaults unless you delegated elsewhere.
AWS Route 53
Hosted zone → create/update A record alias or value for the apex.
Copy the four Route 53 nameservers to your domain registrar's NS settings.
Allow propagation after NS changes (can take up to 48 hours).
After migrating hosts
Get the new server IP from your new host before switching.
Update A record (or change nameservers if DNS moves too).
Keep old site running until TTL expires; do not delete old DNS until the new records resolve globally.
WordPress / cPanel hosting
Hosting panel usually shows the IP to use for your A record.
If the host manages DNS, update there; if not, update at your registrar.
Some hosts use CNAME for www — ensure apex A record exists for root-domain scans.
How to verify the fix
Document nameserver and A record values before any migration.
Use a global DNS propagation checker before declaring the fix complete.
Re-scan with Plexa Trust and confirm "DNS Resolution Issue" is cleared.
Set sensible TTLs (300–3600s) during change windows.
Common mistakes
Changing nameservers without creating records at the new DNS host first.
Leaving an A record pointing at an old IP after server migration.
Editing DNS at the registrar when the domain uses external nameservers (changes have no effect).
Expecting instant global propagation — respect TTL.
Frequently asked questions
What is an A record?
A DNS record mapping a hostname to an IPv4 address — e.g. example.com → 93.184.216.34.
Why did my site break after changing nameservers?
The new DNS host may not have your records yet. Copy all records before switching NS, or recreate them immediately.
How long does DNS propagation take?
A record changes: often 15–60 minutes. Nameserver changes: up to 48 hours. TTL controls cache duration.
What is the difference between DNS at registrar vs Cloudflare?
Whoever hosts the nameservers listed at your registrar is authoritative. Edits elsewhere are ignored.
Do I need both A and CNAME for www?
Common pattern: A on apex, CNAME www → apex or A on both. The apex cannot be a CNAME per DNS rules — use A or ALIAS.
Can DNS issues affect email only?
Yes — MX records are separate from A records. A site can load while email fails if MX is wrong, and vice versa.
What if nslookup works for me but not others?
Propagation is not complete, or different resolvers cache old data. Wait for TTL or check from another network.
How do I confirm the fix?
Global DNS checker shows correct IP everywhere; Plexa Trust re-scan clears "DNS Resolution Issue".
Think you've fixed it?
Run a free scan to verify the issue is resolved. Upgrade to Pro on Plexa Trust for the full audit, monitoring alerts, and score history.
Verify with a free scan