Since roughly 13:00 UTC today, we have recorded errors in the DNS resolution for epizy.com.
Subdomains of epizy.com are unreachable
If you do need your website to be reachable urgently, you can of course create an additional subdomain for your hosting using another domain name. You can do so through the Subdomains section in your control panel.
To fix this, you can change the nameservers at your domain registrar from ns1.epizy.com and ns2.epizy.com to ns1.byet.org and ns2.byet.org. These addresses point to the same nameservers and will respond with the right DNS settings.
If your domain name is using our mail service, it’s probably configured to use
mx.epizy.com as the MX record. Since this record is currently unreachable, you can use
If you’re using third party nameservers like Cloudflare, you may have configured those nameservers to point to the main domain name of your hosting account. Since the main domain usually includes epizy.com, this may affect the status of your domain name as well.
To fix this, you can remove the CNAME records with your main domain, and replace them with A records pointing to your website IP address. To figure out your website IP address, you can use this tool. Simply replace the domain name in the top left box with your account’s main domain (yes, the broken one) and click Dig. The IP address just below there, which looks like 185.27.134.XXX, is the IP address of your hosting account.
The issue appears to be caused by an error at the root nameservers for the .com domain extension. These nameservers should normally return the configured nameservers for .com domains, but don’t appear to do so for the epizy.com domain name.
We’re currently trying to get in touch with our domain registrar NameSilo to get this issue resolved. Unfortunately, they have been unable to resolve the problem so far.
UPDATE: The DNS issue with the epizy.com domain has been fixed by NameSilo around 4:00 UTC this morning. The domain name should be accessible again from everywhere, and all the issue described above should have been fixed.
That said, due to DNS propagation, it can still take a day for everything to be accessible again everywhere.