I have created this website - victoriaducks.rf.gd. 3 days ago but still cannot access it for some reason. It refers me to advertisement page instead.
I did everything flushed my dns, cleared my browser cache and waited 3 days. Still cannot access it.
For me it works for some reason. Many topics were created about the same issue, but it seems like some locations are affected by that issue. Can you please do a traceroute of ns1.epizy.com? That should also show the location you’re trying to connect to to resolve your DNS.
This is what I get:
Tracing route to ns1.epizy.com [198.251.86.152]
over a maximum of 30 hops:
1 6 ms 3 ms 3 ms hitronhub.home [192.168.0.1]
2 * * * Request timed out.
3 11 ms 13 ms 12 ms 64.59.161.193
4 21 ms 11 ms 12 ms 66.163.72.22
5 18 ms 16 ms 17 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6 46 ms 51 ms 47 ms any2ix.coresite.com [206.72.211.134]
7 48 ms 42 ms 47 ms lax-cs1-02gw.voxility.net [37.221.175.53]
8 45 ms 44 ms 44 ms lax-cs1-01c.voxility.net [5.254.87.218]
9 56 ms 52 ms 50 ms ns4.byet.org [198.251.86.152]
Trace complete.
Thank you for sharing the traceroute!
Your message, and those from others, have clearly helped to indicate that the Los Angeles DNS servers were malfunctioning. This has been corrected now. Can you please check if your domain works now?
Unfortunately, I am still having this issue. Below is my new trace route:
C:\Users\Anar>tracert ns1.epizy.com
Tracing route to ns1.epizy.com [198.251.86.152]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms 10.0.0.1
2 15 ms 14 ms 15 ms 70.66.224.1
3 17 ms 18 ms 14 ms 64.59.161.245
4 19 ms 20 ms 28 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
5 53 ms 51 ms 49 ms any2ix.coresite.com [206.72.211.134]
6 49 ms 51 ms 47 ms lax-cs1-02gw.voxility.net [37.221.175.53]
7 50 ms 61 ms 47 ms lax-cs1-01c.voxility.net [5.254.87.222]
8 59 ms 59 ms 52 ms ns4.byet.org [198.251.86.152]
Trace complete.
I checked the DNS for your domain from our own monitoring node in Los Angeles, which returned the correct DNS records.
Do you still get the DNS domain not found error? If so, this may just be caching at your DNS resolver, rather than an issue with our nameservers. You could try to clear your computer’s DNS cache or try another DNS resolver like Google Public DNS or Cloudflare’s 1.1.1.1 service.
Yeah, thank you problem solved!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.