I have configured my domain DSODiary.com with Cloudflare around 10 days ago. DNS propagation completed almost immediately though I am not able to access my website.
I tried some VPN/Tor/Mobile network and voila! I am not able to understand why the propagation has not completed for most of the Internet service providers except Mobile network.
$ traceroute sitemeer.com
traceroute: Warning: sitemeer.com has multiple addresses; using 104.22.1.130
traceroute to sitemeer.com (104.22.1.130), 64 hops max, 52 byte packets
1 192.168.1.253 (192.168.1.253) 2.020 ms 1.378 ms 2.438 ms
2 192.168.0.251 (192.168.0.251) 4.626 ms 2.831 ms 1.563 ms
3 static-mum-182.57.128.1.mtnl.net.in (182.57.128.1) 10.788 ms 6.008 ms 4.543 ms
4 static-mum-59.185.211.73.mtnl.net.in (59.185.211.73) 6.211 ms
static-mum-59.185.210.197.mtnl.net.in (59.185.210.197) 6.334 ms
static-mum-59.185.210.49.mtnl.net.in (59.185.210.49) 5.198 ms
5 static-mum-59.185.211.74.mtnl.net.in (59.185.211.74) 5.277 ms
static-mum-59.185.210.198.mtnl.net.in (59.185.210.198) 5.302 ms
static-mum-59.185.210.50.mtnl.net.in (59.185.210.50) 6.099 ms
6 125.18.8.105 (125.18.8.105) 6.242 ms
static-mum-59.185.211.225.mtnl.net.in (59.185.211.225) 6.217 ms
125.18.8.105 (125.18.8.105) 6.552 ms
7 182.79.203.22 (182.79.203.22) 5.569 ms
125.18.8.105 (125.18.8.105) 6.711 ms
182.79.203.46 (182.79.203.46) 5.631 ms
8 182.79.223.54 (182.79.223.54) 8.827 ms
182.79.203.201 (182.79.203.201) 6.974 ms
182.79.223.54 (182.79.223.54) 7.104 ms
9 104.22.1.130 (104.22.1.130) 6.444 ms
182.79.223.54 (182.79.223.54) 13.347 ms
104.22.1.130 (104.22.1.130) 5.902 ms
I understand that there is some issue from ISP end but I have tried multiple ISP and none of them open my site, however I am able to open it using TOR. I tried Setting SOA with Cloudflare but later learnt that Cloudflare by default sets it that can’t be modified. What do you suggest, why ISP is blocking it, not one but all.
It hosted on AWS. So blacklisted IP from AWS you mean ?
I have hosted like 10s of application on Cloudflare and 100s on AWS. This is the first time I am facing such issue.
Also, what bugs me is what anticipated propagation time I should share to my client going forward which as documented shouldn’t take more than 72 hours. Very weird, I must say.