When your website displays "This site can't be reached" or similar errors, DNS (Domain Name System) issues are usually the cause. DNS acts as the internet's address book, translating your domain name into the IP address where your website lives. If you just changed nameservers, pointed your domain to new hosting, or updated DNS records within the last 48 hours, you're likely experiencing DNS propagation. This is normal and temporary. DNS changes don't happen instantly, they spread gradually across thousands of servers worldwide, taking anywhere from 15 minutes to 48 hours to complete. During this period, some visitors see your site while others get errors. The only solution is patience, no amount of troubleshooting will speed up global propagation.
This guide addresses the most common DNS errors and provides step-by-step solutions to get your site back online.
The Usual Suspects: Propagation and Cache
DNS Propagation Delay
When you make DNS changes at NameSilo (changing nameservers, updating A records, adding new DNS entries), these updates must propagate to DNS servers operated by ISPs, mobile carriers, and content delivery networks worldwide. Different servers update at different speeds based on their refresh schedules.
During propagation, your site may load at home but not at work, work on mobile but not desktop, or function in some geographic locations while failing in others. This inconsistency is expected. Most changes complete within 4-24 hours, though worst-case scenarios extend to 48 hours.
Use online DNS checker tools to verify propagation status. If results show mixed IP addresses (some showing your old hosting IP, others showing the new one), propagation is still in progress.
Local DNS Cache
Your computer, phone, and router all cache DNS lookups to speed up browsing. When you change DNS records, these devices continue using the old cached information until their local cache expires or gets manually cleared.
This causes a specific pattern: your site works when tested from external tools or other devices, but fails on your computer. The DNS changes are live globally, but your device is stuck viewing outdated information.
The solution is flushing your local DNS cache, which forces your device to request fresh DNS data from authoritative servers.
Common DNS Error Codes Explained
NXDOMAIN (Non-Existent Domain)
The DNS system cannot find any records for your domain. Either the domain doesn't exist in DNS, or no A records point it to a web server. Common causes include never adding A records after registration, accidentally deleting records, or the domain expiring.
Log into your NameSilo Domain Manager, click the blue globe icon, and verify A records exist pointing to your hosting IP. DNS_PROBE_FINISHED_NXDOMAIN
This Chrome error typically indicates local DNS cache problems rather than actual DNS misconfiguration. If the domain resolves on mobile data or through online DNS checkers but fails on your computer, local cache is holding outdated information.
SERVFAIL
The DNS server encountered an error resolving your domain. Usually caused by nameservers pointing to non-functional DNS servers, DNS hosting provider outages, or circular dependencies in configuration.
ServerHold or ClientHold Status
These statuses prevent DNS resolution entirely. Common causes: ICANN verification email not confirmed within 15 days, payment disputes, or legal holds. Check domain status in NameSilo WHOIS and look for pending verification emails.
Step-by-Step DNS Fixes
Fix 1: Flush Your Local DNS Cache
Clearing your device's DNS cache forces it to retrieve fresh DNS information from authoritative servers.
- Open Command Prompt as Administrator (search "cmd", right-click, select "Run as administrator")
- You'll see confirmation: "Successfully flushed the DNS Resolver Cache"
- Open Terminal (Applications → Utilities → Terminal)
- Type:
sudo killall -HUP mDNSResponder
- Enter your password when prompted (characters won't display as you type)
Most distributions use systemd-resolved: sudo systemd-resolve --flush-caches
For older systems using nscd: sudo /etc/init.d/nscd restart
Restart your router: After flushing device cache, power cycle your router by unplugging it for 30 seconds. Routers maintain their own DNS cache separate from your computer.
Fix 2: Verify DNS Records in NameSilo
Incorrect or missing DNS records are the most common cause of persistent DNS errors after propagation completes.
Step 1: Log into your NameSilo account and navigate to Domain Manager
Step 2: Click the domain name and then select the “DNS” Tab
Step 3: Review your A records
You should see at minimum:
- An A record for @ (root domain) pointing to your hosting IP
- An A record for www pointing to the same IP (or a CNAME for www pointing to @)
Common mistake: NameSilo domains start with default parking page records. When you add your hosting provider's IP, you must DELETE the old parking records. Having both creates conflicts where some visitors see your site while others see the NameSilo parking page.
Step 4: Verify nameserver settings
On the “Quick Settings” tab, check which nameservers your domain uses:
- NameSilo DNS nameservers: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com - You manage records through NameSilo's DNS interface
- NameSilo hosting nameservers: ns1.hostsilo.com, ns2.hostsilo.com - Your domain uses NameSilo's hosting DNS
- Custom nameservers: If you see other nameservers (Cloudflare, your hosting company, etc.), you manage DNS records at that provider, not at NameSilo
Fix 3: Check for Conflicting Records
Delete any old A records pointing to previous hosting IPs. Multiple A records for the same hostname cause round-robin behavior where DNS randomly returns different IPs, creating intermittent access issues. NameSilo domains start with default parking page records - when adding your hosting IP, delete all records with "PARKED" in the name.
DNS Error Reference Table
| | |
This site can't be reached | DNS propagation in progress | Wait 24 hours after DNS changes |
| | Add A records in DNS Manager |
DNS_PROBE_FINISHED_NXDOMAIN | | Flush DNS cache on your device |
| Nameserver misconfiguration | Verify nameservers at registrar |
| | Check with hosting provider |
DNS address could not be found | Nameservers not responding | Contact DNS provider support |
| Domain verification required | Check email for ICANN verification |
Avoiding Future DNS Problems
Before making DNS changes, screenshot your current records so you can revert if needed. Make changes during low-traffic periods (nights/weekends) and test configurations on staging subdomains before updating primary domains.
What This Means for You
DNS troubleshooting follows a logical progression: Check if you made changes within 48 hours (propagation is the cause - wait). Clear local DNS cache on your device and router (solves 80% of persistent errors). Verify DNS records in NameSilo point to correct IPs and remove conflicting entries. Test using external DNS checkers to determine if issues are local or global. If DNS fails after 48 hours with correct records and cleared caches, contact NameSilo support or your hosting provider with specific error messages.
Frequently Asked Questions
How long does DNS propagation actually take?
DNS propagation typically completes within 4-24 hours, though the theoretical maximum is 48 hours. Changes to A records usually propagate faster than nameserver changes. You cannot speed up propagation - it depends on TTL settings and external DNS server refresh schedules.
Why does my site work on some devices but not others?
Different devices use different DNS servers which update at different speeds. Your computer might use Google DNS (8.8.8.8), your phone uses carrier DNS, and your workplace uses corporate DNS - each cached different information.
Should I use NameSilo's nameservers or my hosting company's nameservers?
Both work, but the choice affects where you manage DNS. Using NameSilo's DNS nameservers (ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com) means managing all DNS records through NameSilo's interface. If you use NameSilo hosting, your domain will use ns1.hostsilo.com and ns2.hostsilo.com automatically. Using your external host's nameservers means managing DNS through your hosting control panel. Choose based on which interface you prefer.
Why do I see a NameSilo parking page instead of my website?
Default parking records still exist in your DNS. You added your hosting IP but didn't delete the parking records, creating a conflict. Log into DNS Manager, delete all records with "PARKED" in the name, and ensure only your hosting IP appears in the A records.
Can DNS errors affect email delivery?
Yes. Email uses MX records (a type of DNS record). If DNS isn't resolving for your domain, email won't work either. However, email can function while the website is down if A records are broken but MX records remain correct.
.png&w=3840&q=75)
.png&w=2048&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)