If you get this conduct after an ongoing update to your site or a recently made package, you're more likely to encounter a DNS propagation delay.
It will resolve itself in few hours.
The presumption is that when you recently visited your site you visited utilizing www.domain.com and not domain.com (without the www). Along these lines, your DNS resolvers have the query of www.domain.com put away in their store. When you attempt to see www.domain.com once more, you get your DNS resolvers' stored esteem which is the old IP address. Nonetheless, when you checked the space with just "domain.com" (no www) your DNS resolvers didn't have an answer in their reserve so got the new (right) IP address for the area. Henceforth "domain.com" works for you however "www.domain.com" doesn't.
The main arrangement here is to trust that the cache will terminate on your resolver, and after that when you visit the domain again a fresh lookup will be made and the new IP will be stored.
In case you're utilizing the HamroDNS nameservers, this should take no longer than 60 minutes.
