Hello. Website english.credit not displaying globally, only in North America at the present time. I changed DNS to epizy servers about 4 days ago, so it’s been more than enough time to properly propogate.
I contacted the registrar, they said all is setup correctly at their end. They suggested i contact the hosting provider as there could be some issues.
thank you but where exactly is the solution? I need people in asia and australia to see my website but they can’t and i dk why? it is a newly registered domain name so it’s not in anyone’s cache anywhere.
As I can see this domain is currently pointed to a third-party hosting provider.
yes im using a custom domain
As it is only possible to ban certain IP addresses only on the hosting provider’s side please contact them to check the possible blocking filter.
oh maybe the IP address is blocked?
It is most probably that indeed the IP addresses are blocked as they determine the location of certain users.
my only explanation why it’s only being seen in north america is even though it’s been 4 days since i changed the DNS to point to epizy servers, possibly for some strange reason it’s not properly propogated globally as of yet. (hasnt gone through the pipe to the computers on the other side of the world).
My second hunch is some form of blocking of EPIZY servers (the IP’s), I have my DNS pointing to epizy1 and epizy2 , perhaps if i were to change them to other nameservers, the IP would also change but i dont know this…??? (example: maybe an epizy 4 or 5??)
You can clear your computer’s DNS cache to force your computer to look up your domain name again. cPanel has written instructions on how to clear DNS cache on various operating systems. You can read their instructions here.
Note that this will only clear the DNS cache on your own computer, not the cache with your DNS Resolver. If your DNS Resolver still has the old records cached, you will not see your website.
Edit your hosts file to override DNS settings
Instead of doing a DNS lookup, your computer also has a so-called hosts file. This file can point domain names to IP addresses on your own computer, and will be checked before any DNS lookup is done. So you can change the hosts file of your computer to point your domain name to your new IP address, before the DNS cache has cleared (or even before any DNS changes have been made).
HowToGeek has a great article on how to make changes to your computer’s hosts file here. You can find the website’s IP address to use by following this guide.
Switch to a better DNS resolver
One of the biggest problems with DNS caching is that DNS Resolvers can cache their results for a long time, and there is no way to clear their caches unless you operate the DNS Resolver yourself.
Fortunately, you are (generally) not forced to use the DNS Resolver provided by your internet provider. Many routers and most devices offer ways to configure your own DNS Resolvers. There are a few great DNS resolvers available for everyone to use. Many of these DNS resolvers don’t cache results as long as the resolvers operated by internet providers, and are sometimes even faster!
Which DNS resolver is the fastest for you depends on your location and your network connection. In order to figure out which provider is the fastest (and check some other options) you can use a tool like Namebench to test and compare DNS resolvers.
Where did you get those ping results from? From other people running it on their own computer or from some online tool?
The IP addresses of our nameservers are provided from multiple locations around the world. But the number of people reporting random DNS issues makes me suspect that some of these locations are malfunctioning. That would explain the random DNS issues for some people while other people do not have these problems.
Could you please make a traceroute from one of these error locations to ns1.epizy.com and share them here? The traceroute will show which location you connect to to resolve your DNS.
Tampa - US - Could not run test as location server may be down.
I’m not sure whether that’s a false positive on the monitoring side or actually a hosting issue. The traceroute from Tampa goes to Ashburn, which appears to be working fine from my own monitoring side.
The Paris error sounds like it’s an issue with the connection to the website server rather than with the DNS server. But the websites are not globally distributed, so there should not be any difference depending on where in the world you are.