www.domain.com doesn’t work, but domain.com works fine (or vice-versa)

If you get this behaviour after a recent update to your website or a newly created package, you are almost certainly experiencing DNS propagation which will resolve itself in a matter of hours.

The assumption is that when you previously visited your website you visited using www.domain.com and not domain.com (without the www). Thus, your DNS resolvers have the lookup of www.domain.com stored in their cache. When you try to view www.domain.com again, you get your DNS resolvers cached value which is the old IP address. However, when you checked the domain with just "domain.com" (no www) your DNS resolvers did not have an answer in their cache so fetched the new (correct) IP address for the domain - hence "domain.com" works for you but "www.domain.com" does not.

The only solution here is to wait for the cache to expire on your resolver, and then when you visit the domain again a fresh lookup with be made and the new IP will be stored. If you have recently changed your nameservers, or would like to read more about DNS propagation, please check out What is DNS Propagation?

  • 0 Benutzer fanden dies hilfreich
War diese Antwort hilfreich?

Verwandte Beiträge

What is DNS Propagation?

When you make a change to your DNS records or update your domains nameservers, you need to wait a...

How can I tell if DNS has propagated for me?

If you are unsure whether DNS has fully propagated for you, you should check the IP address your...

TXT Records

TXT (or text) records are not generally used to locate servers on the Internet, but to prove to...

What is domain propagation?

DNS propagation defines the process of updating information across the internet. There are two...

A Records

A records allow a DNS name (eg, www.2host.ch) to be pointed to 1 or more IPv4 addresses (quad...

Powered by WHMCompleteSolution