DNS Set But Website Still Unreachable? Here’s How to Fix It Like a Pro

You've configured your DNS servers, pointed your domain to the right IP, and waited — yet your website is still unreachable. Sound familiar? This is one of the most common and frustrating situations in web hosting, and the root cause isn't always obvious. Whether you're seeing a "Server Not Found" error, a blank page, or a timeout, the problem could stem from DNS propagation delays, misconfigured records, stale cache data, or server-side issues.

This comprehensive guide walks you through every likely cause and provides clear, actionable troubleshooting steps to get your website back online as quickly as possible.

1. Understanding DNS and Why It Matters for Website Accessibility

The Domain Name System (DNS) is essentially the internet's phonebook. When a user types your domain name (e.g., example.com) into their browser, DNS servers translate that human-readable name into a machine-readable IP address, allowing the browser to locate and connect to your web server.

When DNS is misconfigured or hasn't fully propagated, browsers can't resolve your domain to the correct IP address. The result: connection errors, timeouts, and an inaccessible website — even if your server is perfectly healthy and running.

Understanding this process is the first step toward diagnosing what's gone wrong.

2. Common Causes of DNS-Related Website Inaccessibility

Before diving into fixes, it's important to understand the most frequent culprits behind DNS failures:

DNS Propagation Delay

DNS changes don't take effect instantly. After updating your nameservers or DNS records, propagation across the global network of DNS resolvers can take anywhere from a few minutes to up to 48 hours. During this window, some users may reach your site while others cannot — depending on which DNS server their ISP uses.

Incorrect DNS Records

A single typo or misconfiguration in your DNS zone file can break everything. Common mistakes include:

• An A record pointing to the wrong IP address
• A CNAME record with an incorrect target hostname
• Missing or misconfigured MX records affecting email delivery

Stale DNS Cache

Your operating system and browser both cache DNS lookups to speed up browsing. If you've recently changed DNS settings, your local machine may still be serving the old, cached IP address — making the site appear unreachable even after propagation is complete.

Firewall and Network Restrictions

Firewalls at the server level, network level, or even on the client side can block traffic to specific IP addresses or ports, preventing the website from loading even when DNS resolves correctly.

Web Server Misconfiguration or Downtime

Sometimes DNS is perfectly fine, but the web server itself is offline, misconfigured, or not listening on the correct ports.

3. Step-by-Step DNS Troubleshooting Guide

Work through these steps in order. Each one narrows down the source of the problem.

Step 1: Check DNS Propagation Status

If you recently updated your DNS settings or migrated to a new host, propagation may simply not be complete yet. Use a free online tool to check the current propagation status across multiple global locations.

How to check:

1. Visit WhatsMyDNS.net
2. Enter your domain name and select the record type (typically A record)
3. Review the results — if different locations return different IP addresses, propagation is still in progress

What to do: If propagation is incomplete, the best course of action is to wait. Most changes propagate within 1–4 hours, though in rare cases it can take up to 48 hours. You can reduce future propagation times by lowering your DNS TTL (Time to Live) value before making changes.

Step 2: Flush Your Local DNS Cache

Even after propagation completes globally, your own computer may still be serving a cached version of the old DNS record. Clearing your DNS cache forces your system to perform a fresh lookup.

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux (Ubuntu/Debian with systemd-resolved):

sudo systemd-resolve --flush-caches

Clear your browser cache as well:

Navigate to your browser's settings, find "Clear browsing data", and make sure cached images and files are included. In Chrome, you can also visit chrome://net-internals/#dns to flush the browser's internal DNS cache directly.

Step 3: Query DNS Records with nslookup and dig

Command-line tools give you direct, unfiltered insight into what DNS is returning for your domain. These are essential for diagnosing misconfigured records.

Using nslookup (available on Windows, macOS, and Linux):

nslookup example.com

Using dig (Linux/macOS; install via Homebrew on Mac):

dig example.com
dig example.com A
dig example.com MX

What to look for:

• The ANSWER SECTION in dig output should show your domain resolving to the correct IP address
• If the IP returned doesn't match your server's IP, your A record is misconfigured
• If there's no answer at all, your DNS zone may not be set up correctly at the registrar level

You can also query a specific DNS server to bypass your local resolver:

dig example.com @8.8.8.8

Step 4: Verify DNS Records in Your Domain Registrar's Control Panel

Log into your domain registrar's dashboard and carefully review your DNS zone settings. Confirm the following records are present and correct:

Common mistakes to check:

• Trailing dots missing in fully qualified domain names (FQDNs)
• Incorrect TTL values
• Duplicate or conflicting A records
• Nameservers not updated after switching hosting providers

If you're hosting with AlexHost VPS Hosting, your nameserver details will be provided in your hosting control panel. Make sure these are entered exactly as specified at your domain registrar. You can also register your domain directly through AlexHost Domain Registration to keep DNS management centralized and simplified.

Step 5: Check Your Web Server Status and Configuration

If DNS resolves correctly but the site is still unreachable, the problem may lie with the web server itself. A server that is stopped, crashed, or misconfigured will refuse connections regardless of how perfect your DNS is.

Check Apache status:

sudo systemctl status apache2

Check Nginx status:

sudo systemctl status nginx

Restart the web server if it's stopped:

sudo systemctl restart apache2
# or
sudo systemctl restart nginx

Check that the server is listening on the correct ports:

sudo ss -tlnp | grep -E ':80|:443'

If nothing is listening on port 80 (HTTP) or port 443 (HTTPS), your web server isn't running correctly. Also verify your virtual host or server block configuration to ensure it's bound to the correct domain and IP.

Step 6: Inspect Firewall Rules

A firewall that blocks inbound traffic on port 80 or 443 will make your website unreachable even when DNS and the web server are both working correctly.

Check UFW (Ubuntu Firewall) rules:

sudo ufw status

Allow HTTP and HTTPS traffic:

sudo ufw allow 80/tcp
sudo ufw allow 443/tcp

Check iptables rules:

sudo iptables -L -n

Also check your hosting provider's firewall or security group settings if you're on a cloud or VPS platform. These are often managed separately from the OS-level firewall.

Step 7: Run Ping and Traceroute Tests

These network diagnostic tools help you determine whether traffic is actually reaching your server.

Ping test — checks if the domain resolves and if the server responds to ICMP packets:

ping example.com

Note: Some servers block ICMP (ping) requests by default. A failed ping doesn't necessarily mean the server is down.

Traceroute — traces the full network path from your machine to the server, revealing where packets are being dropped:

*Linux/macOS:*

traceroute example.com

*Windows:*

tracert example.com

If the traceroute stops at a specific hop before reaching your server, that node may be experiencing an outage or actively blocking traffic. This information is extremely useful when escalating to your hosting provider.

4. Additional Fixes Worth Trying

Switch to a Public DNS Resolver

Your ISP's DNS server may be slow to update or experiencing issues. Try switching to a faster, more reliable public DNS resolver:

• Google DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1
• OpenDNS: 208.67.222.222 and 208.67.220.220

You can change DNS settings in your network adapter settings (Windows/macOS) or directly on your router to apply the change to all devices on your network.

Disable VPN or Proxy

If you're using a VPN or proxy service, it may be routing your traffic through a location where DNS hasn't propagated yet, or where your server's IP is blocked. Temporarily disable it and test again using your direct internet connection.

Verify SSL Certificate Configuration

If your site loads over HTTP but not HTTPS, the issue may be with your SSL certificate rather than DNS. An expired, misconfigured, or missing certificate will cause browsers to block access to your site. AlexHost offers SSL Certificates that are easy to install and keep your site secure and trusted.

5. Choosing the Right Hosting Infrastructure to Minimize DNS Issues

Many DNS-related problems can be prevented by choosing a reliable hosting provider with robust infrastructure and clear DNS management tools.

• VPS Hosting — Ideal for developers and businesses that need full control over their server environment, including custom DNS configurations and firewall rules.
• Dedicated Servers — Best for high-traffic websites that require maximum performance, dedicated IP addresses, and complete server isolation.
• Shared Web Hosting — A cost-effective option for smaller websites, with DNS managed through an intuitive control panel.
• VPS with cPanel — Combines the power of a VPS with the user-friendly cPanel interface, making DNS record management straightforward even for non-technical users.

6. When to Contact Your Hosting Provider

If you've worked through all of the steps above and your website is still unreachable, it's time to escalate. Your hosting provider's support team can:

• Verify that your server is online and reachable from their network
• Check for IP-level blocks or routing issues on their end
• Review server logs to identify application-level errors
• Confirm that your DNS zone is correctly configured on their nameservers

When contacting support, provide the output of your dig, ping, and traceroute commands — this dramatically speeds up the diagnostic process.

Conclusion: Systematically Diagnose and Fix DNS Issues

An unreachable website after setting DNS servers is almost always traceable to one of a handful of root causes: propagation delays, misconfigured records, stale cache data, firewall blocks, or web server downtime. The key is to work through the problem methodically rather than guessing.

Quick troubleshooting checklist:

• ✅ Check DNS propagation with WhatsMyDNS
• ✅ Flush DNS cache on your OS and browser
• ✅ Query DNS records with nslookup and dig
• ✅ Verify all DNS records in your registrar's control panel
• ✅ Confirm your web server is running and listening on ports 80/443
• ✅ Review firewall rules for blocked traffic
• ✅ Run ping and traceroute to identify network-level issues
• ✅ Try switching to Google DNS or Cloudflare DNS
• ✅ Disable VPN or proxy temporarily

By following this guide, you'll be equipped to identify and resolve virtually any DNS-related connectivity issue. And if you need expert assistance, AlexHost's support team is available around the clock to help you restore access and keep your website running smoothly.