Skip to content
Hosting Operations8 min read

DNS Not Resolving: Step-by-Step Fix

DNS not resolving? Compare common causes, test with real commands, and apply the right fix for your setup. Follow this evergreen troubleshooting guide.

Written by Abdul AbrorTechnical Hosting Support Engineer
Two dice with gop and dnc symbols
On this page

TL;DR — Key takeaways

  • Start with a single failing domain, then test from multiple networks and devices before changing anything.
  • Check local resolvers, ISP behavior, and firewall rules before assuming your nameserver is broken.
  • Compare public resolvers, custom DNS providers, and managed DNS platforms to match your traffic and control needs.
  • Back up current records and test changes on a subdomain before applying them globally.
  • Use TTL reduction and a rollback plan when you must push changes quickly.

DNS failures are common, but the root cause is usually one of a few predictable places. A domain may resolve from one network and not another, or it may work in the browser but fail in an API call. This guide walks through the actual steps I use when a domain stops resolving, with a clear comparison of the options you can choose from.

You will not need to guess. Start with a single failing domain, test it from different networks, and then move from the local machine to the nameserver. Each step removes one variable until the cause is clear.

What DNS Not Resolving Actually Means

DNS not resolving means a client cannot turn a domain name into an IP address. The request may fail at the local resolver, the ISP cache, a firewall, or the authoritative nameserver. The symptom is the same, but the cause changes based on where the lookup stops.

A quick way to separate the layers is to test with a known-good domain. If google.com resolves but your domain does not, the problem is likely in your zone or your local configuration. If nothing resolves, the issue is closer to the network or the local resolver.

  • Local resolver: your machine or network DNS setting.
  • ISP or public resolver: the service that answers the query.
  • Firewall or proxy: blocks UDP or TCP port 53.
  • Authoritative nameserver: the zone or record is wrong or unreachable.

Step-by-Step Fix for DNS Not Resolving

Start with the smallest, safest change and work upward. Do not change your nameserver until you have confirmed the zone file and local resolver are correct.

First, run a lookup from your local machine. Use dig or nslookup with a public resolver. If the query fails, test the same domain from a different network or device. This tells you whether the issue is local or global.

Next, check the nameserver itself. Query the authoritative server directly with dig @nameserver domain. If that works, the problem is in your local resolver or network path. If it fails, the zone or nameserver configuration is the likely culprit.

Then review the zone file. Check for typos, missing records, and correct TTL values. A single bad character can stop resolution for the whole domain.

Finally, apply changes carefully. Back up the current zone file, test on a subdomain, and lower the TTL before pushing global changes.

  • Run dig +short domain @8.8.8.8 from a local machine.
  • Test the same domain from a different network or mobile hotspot.
  • Query the authoritative nameserver directly with dig @ns1.example.com domain.
  • Check zone file syntax, TTL, and record types.
  • Back up the zone file before making changes.
  • Test on a subdomain before applying changes globally.

Compare DNS Options: Public Resolvers, Custom DNS, and Managed DNS

Three main paths exist for handling DNS. Public resolvers are fast to test and easy to switch. Custom DNS gives you full control over records and zone files. Managed DNS platforms add support, analytics, and failover, but they cost more and may lock you into a provider.

Public resolvers like 8.8.8.8 and 1.1.1.1 are useful for troubleshooting. They answer queries quickly and are easy to point at during testing. They are not a long-term hosting solution for most domains.

Custom DNS means you run or manage your own nameservers. This gives you full control and no recurring provider fee, but it requires monitoring, updates, and a reliable network path. It works well for infrastructure teams that already run their own services.

Managed DNS is the middle ground. You delegate your domain to a provider, they host the zone, and they handle updates and support. This is the best fit for most website owners who want stability without managing nameservers directly.

  • Public resolvers: fast testing, no control, easy to switch.
  • Custom DNS: full control, higher maintenance, no provider fee.
  • Managed DNS: support and analytics, higher cost, less hands-on work.

When to Use Each Option

Choose a public resolver if you are troubleshooting and need a quick second opinion. Point your dig command at 8.8.8.8 or 1.1.1.1 and see if the domain responds. This does not fix your setup, but it tells you where the failure happens.

Choose custom DNS if you already run your own infrastructure, need full control over records, or want to avoid recurring provider costs. This path requires you to monitor uptime, manage zone files, and keep the nameserver network stable.

Choose managed DNS if you want predictable uptime, support, and analytics without managing nameservers. It is the safest default for most website owners, especially when you rely on email, subdomains, or multiple records.

Some teams use a hybrid approach. They keep public resolvers for testing, run custom nameservers for their own domains, and use managed DNS for customer-facing zones. Match the option to your team size, budget, and risk tolerance.

  • Public resolver: quick testing and comparison.
  • Custom DNS: full control and no provider fee.
  • Managed DNS: support, analytics, and lower maintenance.
  • Hybrid setup: testing plus production separation.

Safe Testing Boundaries and Rollback

Never change your production nameserver without a rollback plan. Start by backing up the current zone file. Then test on a subdomain or a staging environment before applying changes globally.

Lower the TTL to 300 or 600 seconds before a change. This shortens the refresh window and reduces the time users see a broken domain. After the change, monitor resolution from multiple networks for at least 24 hours.

If a change breaks something, restore the backup zone file and revert the nameserver delegation. Do not wait for a scheduled maintenance window if users are affected. Rollback first, then investigate.

Keep a change log with the date, the command you ran, and the result. This makes it easier to spot patterns when the same issue returns.

  • Back up the zone file before any change.
  • Test on a subdomain before applying globally.
  • Lower TTL to 300 or 600 seconds before changes.
  • Restore the backup zone file if resolution breaks.
  • Monitor from multiple networks for 24 hours after a change.

Final Recommendation

For most website owners, managed DNS is the safest choice. It removes the need to run your own nameservers while giving you support, analytics, and predictable uptime. Use a public resolver for testing, and keep custom DNS only if you already run your own infrastructure.

If your domain resolves from one network but not another, start with local settings and firewall rules. If it fails everywhere, check the zone file and the authoritative nameserver. Apply changes in small steps, back up your work, and test before you commit.

DNS not resolving is rarely a single mystery. It is usually a missing record, a bad TTL, a local cache, or a firewall rule. Follow the steps in order, compare your options, and you will find the cause without guessing.

  • Managed DNS is the best default for most website owners.
  • Public resolvers are for testing, not long-term hosting.
  • Custom DNS suits teams that already run their own infrastructure.
  • Back up the zone file before every change.
  • Lower TTL before global changes and monitor for 24 hours.

Quick troubleshooting checklist

  • Run dig or nslookup against the failing domain from at least two networks.
  • Verify the local resolver and ISP behavior with a known-good domain.
  • Check firewall, security group, and proxy rules that may block UDP or TCP port 53.
  • Compare public resolvers such as 8.8.8.8 and 1.1.1.1 for consistent results.
  • Review current DNS records, TTL values, and zone file syntax.
  • Back up the zone file before making changes.
  • Test the change on a subdomain or staging environment first.
  • Monitor resolution for 24 to 48 hours after applying global changes.

FAQ

Why does DNS not resolve for one domain but work for others?

A single failing domain usually points to a misconfigured zone, stale cache, or a local network issue. Test the domain from multiple networks and compare it with a known-good domain to isolate the cause.

How long does DNS propagation take after a change?

Propagation is not guaranteed by time alone. It depends on the TTL value, caching layers, and how quickly resolvers refresh. Lower the TTL before a change and monitor resolution from multiple locations.

Which DNS provider should I choose for a small website?

Choose a managed DNS provider if you need fast support, analytics, and automatic failover. Choose a public resolver for quick testing and a custom setup if you need full control over records and zone files.