My www.domain.com doesn’t work, but domain.com works fine

Author:

Published:

Updated on August 15, 2024

Reading Time: 1 min read

Domain with www. is not working #

If you experience this behaviour after a recent update to your website or a newly created package, you’re almost certainly encountering a DNS propagation delay.

It will resolve itself in a matter of hours.

The assumption is that when you previously visited your website, you used 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 didn’t have an answer in their cache, so they fetched the new (correct) IP address for the domain. Hence, “domain.com” works for you, but “www.domain.com” doesn’t.

The only solution here is to wait for the cache to expire on your resolver. When you visit the domain again, a fresh lookup will be made, and the new IP will be stored.

If you’re using the StackDNS nameservers, this should take no longer than 1 hour. If you’ve recently changed your nameservers or would like to read more about DNS propagation, please refer to the “What is DNS Propagation?” section on CP CLOUD HOSTING.