Understanding DNS Resolution
DNS converts domain names to IP addresses. When it fails, you cannot reach your server by domain.
Test DNS Resolution
# Check if DNS resolves
nslookup yourdomain.com
dig yourdomain.com
host yourdomain.com
# Check specific DNS server
dig @8.8.8.8 yourdomain.com
Fix 1: Check Local DNS Cache
Flush local DNS cache:
# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux (systemd-resolved)
sudo systemd-resolve --flush-caches
Fix 2: Check /etc/hosts
Local overrides can block resolution:
cat /etc/hosts
# Remove any entries for your domain if incorrect
Fix 3: Verify DNS Records
Check your domain DNS settings in Hostxpeed panel or registrar:
# Check A record
dig A yourdomain.com
# Check NS records
dig NS yourdomain.com
# Check CNAME
dig CNAME www.yourdomain.com
Fix 4: Check Nameservers
Ensure domain is pointing to correct nameservers:
whois yourdomain.com | grep -i "name server"
Fix 5: DNS Propagation
After DNS changes, propagation can take 24-48 hours:
# Check from different locations
https://dnschecker.org
Fix 6: Check DNSSEC
Invalid DNSSEC signatures break resolution:
dig +dnssec yourdomain.com
Disable DNSSEC temporarily to test.
Fix 7: Use Alternative DNS
Test using Google DNS (8.8.8.8) or Cloudflare (1.1.1.1):
dig @1.1.1.1 yourdomain.com