Back to Fix-It Hub

DNS Not Resolving: Complete Fix Guide 2026

Your domain name isn't resolving? Learn how to diagnose DNS issues, fix DNS propagation problems, and troubleshoot domain name resolution errors.

Updated January 4, 2026
DMV Web Guys
TL;DR
  • DNS not resolving means your domain name can't be found—browser can't connect to your server
  • Common causes: incorrect DNS settings, propagation delays, nameserver issues, or DNS server problems
  • Check DNS propagation using online tools like whatsmydns.net
  • Verify DNS records match your hosting provider's requirements
  • DNS changes can take up to 48 hours to propagate globally

Understanding DNS Resolution

DNS (Domain Name System) translates human-readable domain names (like example.com) into IP addresses (like 192.0.2.1) that computers use to connect to servers.

When DNS doesn't resolve:

  • Browser can't find your website
  • Domain name doesn't work
  • Email may not work
  • Services can't connect

Why it matters:

  • Site is inaccessible
  • Email delivery fails
  • Business operations disrupted
  • Customer access blocked

Website troubleshooting showing DNS and connectivity issues

Photo by Markus Spiske on Pexels

How to Check If DNS Is Resolving

Method 1: Ping Test

Command:

ping yourdomain.com

What to look for:

  • IP address returned = DNS working
  • "Could not find host" = DNS not resolving
  • Timeout = DNS or connectivity issue

Method 2: nslookup

Command:

nslookup yourdomain.com

What to look for:

  • IP address shown = DNS working
  • "Non-existent domain" = DNS not resolving
  • Server information = DNS working

Method 3: Online Tools

DNS checkers:

  • whatsmydns.net
  • dnschecker.org
  • mxtoolbox.com

What they show:

  • DNS propagation status
  • Records from multiple locations
  • Current DNS values
  • Propagation progress

Common Causes

1. Incorrect DNS Settings

Problems:

  • Wrong nameservers
  • Incorrect A records
  • Missing DNS records
  • Typos in records

How to check:

  • Compare with hosting requirements
  • Verify nameservers
  • Check A record IP
  • Review all DNS records

How to fix:

  • Update nameservers
  • Correct A records
  • Add missing records
  • Fix typos

2. DNS Propagation Delay

What it is:

  • DNS changes take time to spread
  • Can take up to 48 hours
  • Different locations see different results

Why it happens:

  • DNS is distributed system
  • Changes propagate gradually
  • Cached DNS records
  • TTL (Time To Live) settings

How to check:

  • Use DNS propagation checker
  • Check from multiple locations
  • Monitor over time
  • Wait for propagation

3. Nameserver Issues

Problems:

  • Nameservers not set
  • Wrong nameservers
  • Nameservers not responding
  • Nameserver propagation delay

How to check:

  • Verify nameservers in domain registrar
  • Test nameserver response
  • Check nameserver propagation
  • Verify with hosting provider

How to fix:

  • Set correct nameservers
  • Update at domain registrar
  • Wait for propagation
  • Verify with hosting

4. DNS Server Problems

Issues:

  • DNS provider down
  • DNS server errors
  • Service outages
  • Configuration problems

How to check:

  • Test DNS server response
  • Check provider status page
  • Test from multiple locations
  • Review error messages

How to fix:

  • Contact DNS provider
  • Wait for service restoration
  • Switch DNS providers if needed
  • Check provider status

5. Domain Registration Issues

Problems:

  • Domain expired
  • Domain suspended
  • Registration problems
  • Transfer in progress

How to check:

  • Verify domain status
  • Check expiration date
  • Review registration details
  • Contact registrar

How to fix:

  • Renew domain if expired
  • Resolve suspension issues
  • Complete registration
  • Wait for transfer completion

Step-by-Step Fix Process

Step 1: Verify DNS Records

Check A record:

  • Should point to server IP
  • Verify IP is correct
  • Check record type
  • Ensure no typos

Check nameservers:

  • Should match hosting provider
  • Verify at domain registrar
  • Check propagation
  • Ensure correct format

Check other records:

  • MX records for email
  • CNAME records
  • TXT records
  • Any other required records

Step 2: Check DNS Propagation

Use propagation checker:

  1. Go to whatsmydns.net
  2. Enter your domain
  3. Select record type (A, NS, etc.)
  4. Check results from multiple locations
  5. Monitor over time

What to look for:

  • Consistent results = Propagated
  • Mixed results = Still propagating
  • No results = Not propagated yet
  • Wrong results = Incorrect records

Step 3: Verify Nameservers

At domain registrar:

  1. Log into registrar account
  2. Find DNS/Nameserver settings
  3. Verify nameservers match hosting
  4. Update if incorrect
  5. Save changes

Common nameserver formats:

  • ns1.hostingprovider.com
  • ns2.hostingprovider.com
  • Or custom nameservers

Step 4: Check TTL Settings

What is TTL:

  • Time To Live
  • How long DNS is cached
  • Lower = faster updates
  • Higher = more stable

For DNS changes:

  • Lower TTL before changes (300-600 seconds)
  • Make DNS changes
  • Wait for propagation
  • Increase TTL after (3600+ seconds)

Step 5: Wait for Propagation

Timeline:

  • Usually: 1-4 hours
  • Sometimes: 24-48 hours
  • Maximum: 72 hours

What to do:

  • Be patient
  • Monitor propagation
  • Check from multiple locations
  • Don't make more changes
  • Wait for completion

Common Scenarios

Scenario 1: New Domain Setup

Problem:

  • Just registered domain
  • DNS not resolving yet
  • Nameservers just set

Solution:

  • Wait for propagation
  • Verify nameservers correct
  • Check DNS records
  • Monitor propagation
  • Usually resolves in hours

Scenario 2: Changed Hosting

Problem:

  • Moved to new host
  • Updated nameservers
  • DNS not resolving

Solution:

  • Verify new nameservers
  • Check A record IP
  • Wait for propagation
  • Clear local DNS cache
  • Monitor progress

Scenario 3: DNS Provider Change

Problem:

  • Switched DNS providers
  • Updated nameservers
  • DNS not working

Solution:

  • Verify nameservers updated
  • Check all DNS records migrated
  • Wait for propagation
  • Test from multiple locations
  • Contact new provider if issues

Troubleshooting Tools

Command Line Tools

ping:

  • Tests basic connectivity
  • Shows if DNS resolves
  • Simple connectivity test

nslookup:

  • Queries DNS servers
  • Shows DNS records
  • Tests resolution

dig:

  • Detailed DNS queries
  • Shows full DNS response
  • Advanced troubleshooting

tracert/traceroute:

  • Shows network path
  • Identifies where connection fails
  • Network troubleshooting

Online Tools

DNS checkers:

  • whatsmydns.net
  • dnschecker.org
  • mxtoolbox.com

What they provide:

  • Propagation status
  • Record values
  • Multiple location checks
  • Historical data

Prevention

Best Practices

Before making changes:

  • Lower TTL values
  • Document current settings
  • Backup DNS records
  • Plan changes carefully
  • Test in staging if possible

When making changes:

  • Update during low traffic
  • Make one change at a time
  • Verify each change
  • Monitor propagation
  • Keep records documented

Regular maintenance:

  • Review DNS records
  • Check expiration dates
  • Monitor DNS health
  • Update as needed
  • Keep documentation current

When to Get Professional Help

Signs You Need Help

Consider hiring if:

  • DNS issues persist after 48 hours
  • Complex DNS setup
  • Multiple domains affected
  • Business-critical impact
  • Unclear about DNS configuration
  • Multiple failed attempts

What professionals can do:

  • Comprehensive DNS audit
  • Configuration optimization
  • Troubleshooting complex issues
  • DNS provider recommendations
  • Ongoing DNS management

Conclusion

DNS resolution issues are common but usually fixable. Verify DNS records, check propagation, and be patient. Most issues resolve within 24-48 hours.

Key takeaways:

  • Verify DNS records are correct
  • Check nameservers match hosting
  • Wait for DNS propagation
  • Use propagation checkers
  • Be patient with changes

The bottom line: Most DNS issues are caused by incorrect settings or propagation delays. Verify your DNS records, ensure nameservers are correct, and wait for propagation. With proper setup, DNS should resolve within 24-48 hours.

For more on domains, check out our domain name guide or learn about DNS basics.

Frequently Asked Questions

DNS not resolving means when someone types your domain name, their computer can't find the IP address of your server. The domain name doesn't translate to an IP address, so the browser can't connect to your website.

Related Articles