DNS Configuration Issues
What This Means
DNS (Domain Name System) configuration issues prevent users from reaching your website by failing to resolve your domain name to the correct IP address. These issues can make your site completely inaccessible or cause intermittent connection failures.
Impact
- Complete site inaccessibility for affected users
- SEO penalties from search engines unable to crawl
- Lost conversions during outages
- Email delivery failures if email DNS records are affected
How to Diagnose
Check DNS Propagation
Use online tools to verify DNS records across global servers:
# Check A record
dig example.com A
# Check all records
dig example.com ANY
# Query specific DNS server
dig @8.8.8.8 example.com
Common DNS Record Types
| Record | Purpose | Example |
|---|---|---|
| A | IPv4 address | 192.0.2.1 |
| AAAA | IPv6 address | 2001:db8::1 |
| CNAME | Alias to another domain | www.example.com |
| MX | Mail server | mail.example.com |
| TXT | Text verification | v=spf1 include:... |
| NS | Name servers | ns1.provider.com |
Signs of DNS Issues
- Site works on some networks but not others
- Recent DNS changes not taking effect
- Timeout errors when accessing the site
- Inconsistent behavior across regions
General Fixes
1. Verify Record Configuration
Ensure all required records are properly configured:
# Required records
A @ 203.0.113.1 # Root domain
A www 203.0.113.1 # WWW subdomain
# or
CNAME www @ # WWW as alias
# Optional but recommended
AAAA @ 2001:db8::1 # IPv6 support
TXT @ "v=spf1 include:..." # Email verification
2. Wait for Propagation
DNS changes can take 24-48 hours to propagate globally:
- TTL (Time to Live) affects propagation speed
- Lower TTL before making changes
- Check propagation status: WhatsMyDNS.net
3. Flush DNS Cache
Clear local DNS cache:
Windows:
ipconfig /flushdns
macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux:
sudo systemd-resolve --flush-caches
4. Verify Nameservers
Ensure correct nameservers are configured at your registrar:
- Check current NS records
- Verify they match your hosting provider's nameservers
- Allow time for NS changes to propagate (up to 48 hours)
Prevention
- Lower TTL before changes - Set to 300 seconds 24 hours before planned changes
- Document DNS configuration - Keep records of all DNS settings
- Test in staging - Verify changes on a test domain first
- Monitor DNS health - Use monitoring services for alerts
Platform-Specific Guides
| Platform | Guide |
|---|---|
| Shopify | Shopify DNS Setup |
| WordPress | WordPress DNS Setup |
| Squarespace | Squarespace DNS Setup |