What to do if your domain is not resolving What to do if your domain...

What to do if your domain is not resolving


Resolving a hostname means to convert a hostname of the form “wwww.domain.com” to an IP address. You can use this DNS lookup tool to check if your hostname is pointing to the correct IP address. There are several reasons why a hostname is not resolving correctly or pointing to the correct place on the internet.

DNS resolution error

Domain registrar

If you are using your own domain name yourdomain.com, the problem may not be with your DNS provider, it could be with your registrar, the registry or something else entirely:

  • The domain name is not registered. To use a custom domain name such as yourdomain.com, you need to first purchase it.
  • The domain name has expired. Domain names are registered for a fixed period of time, commonly 1 year. At the end of this year the domain name needs to be re-registered. Check the expiration date of your domain name here.
  • The domain name could be suspended for some reason. Check the status of your domain name here.

DNS hosting provider

If you are using our DNS service and you are seeing IP address A in the domain current status in the control panel and IP address B when you do a DNS lookup.

  • Check the domain name is using our name servers. You need to update the name servers for your domain name to point to us at your current domain registrar. After you make the change, you can verify the name server change in the WHOIS response.
  • Make sure that the domain name is using only our name servers. If you have our name servers as well as third party name servers listed for your domain name, you will experience random DNS resolution issues.
  • Name server propagation delay. If you have just pointed your domain name to us and the domain name is not resolving correctly, it could be due to name server propagation delay. Check if the name server change has fully propagated here. The name server propagation may take up to 24 hours even though the WHOIS update may take only a few minutes.
Note: If you have secondary DNS service for your domain name, the domain name will be pointing to our name servers and your secondary DNS provider’s name servers.

Other possibilities

  • If you are using your own subdomain sub.yourdomain.com, you need to point the name servers of the subdomain or the primary domain name to us as well. Many DNS service providers do not allow setting up name server records for subdomains.
  • If you are using our web redirect service, your domain name will be resolved to our web redirect server IP address. The web redirect server will then redirect visitors to your website to the URL or port of your choice.
  • If you are using one of our free third level domain names, you do not need to make any name server changes. If your router IP address has changed but the hostname is not pointing to the correct IP address, you need to run an IP update client software to keep the hostname mapped to your current IP address.
  • Your hostname is mapped to the correct IP address but you cannot ping the hostname. This is very normal because not all routers respond to ping requests.

We have covered many of the cases why your hostname is not resolving correctly. Feel free to leave a comment if you can think of any other situations!

David D
June 15, 2017 AT 9:35 AM

What about DNS caching? When a computer visits a website for the first time, it stores the website's DNS information in cache. The next time the computer visits that site, it looks in the cache to see if the website's information is present to use. If the IP address gets updated when the computer is still caching the old result, it could cause problems.


Derek Manning
June 18, 2017 AT 7:44 PM

That's a very good point. DNS caching is used to speed up the name resolution process but could cause some inconveniences if the DNS information has changed. We have a blog on how to clear DNS cache in your computer at https://www.dynu.com/en-US/Blog/Article?Article=How-to-flush-DNS-cache.


David Baker
June 23, 2017 AT 1:26 PM

I noticed that you mentioned using subdomains name.mydomain.com for DDNS service. Most DDNS servir provider does not allow setting up name server records for name.mydomaim.com. What I did was I signed up for a free Dynu third level domain name example.dynu.com and set up a CANME record at my current DNS provider for name.mydomain.com to point to example.dynu.com.


Derek Manning
June 28, 2017 AT 12:12 PM

What you proposed is an excellent idea. Thank you.


Janet Meza
July 12, 2017 AT 1:24 PM

Thank you for this troubleshooting tool. I followed all the steps one by one and was able to locate the reason of my domain name not resolving.


Jayesh Mahato
December 21, 2019 AT 3:04 PM

I am running ddclient in raspbian and the IP is also updated in DYNU panel. I have also set up cronjob as mentioned in one of the articles in this website. However the domain name is not opening up my local website. The local website is running fine in my raspbian. I have allowed all http and dns traffic to the raspbian local ip, in my router. However the website www.projectme24.com simply doesn't load up ever. Please guide.


* (Your email address will not be published.)