DNS Propagation completed still can't access the website

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.

What is missing to get the same working?

Loads fine for me -> http://sitemeer.com/#https://www.dsodiary.com/

Whats the output of these commands?

ping dsodiary.com
nslookup dsodiary.com
ping www.dsodiary.com
nslookup www.dsodiary.com

$ping <domain_name>
PING <domain_name> (104.27.134.181): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
— <domain_name> ping statistics —
7 packets transmitted, 0 packets received, 100.0% packet loss

$ nslookup <domain_name>
Server: 202.159.230.2
Address: 202.159.230.2#53

Non-authoritative answer:
Name: <domain_name>
Address: 104.27.134.181
Name: <domain_name>
Address: *.135.181

$ ping www.<domain_name>
PING www.<domain_name> (104.27.134.181): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
— www.<domain_name> ping statistics —
7 packets transmitted, 0 packets received, 100.0% packet loss

$ nslookup www.<domain_name>
Server: 202.159.230.2
Address: 202.159.230.2#53

Non-authoritative answer:
Name: www.<domain_name>
Address: 104.27.134.181
Name: www.<domain_name>
Address: *.135.181

I have modified output as I can’t post url

DNS resolution seems to work fine.

It rather might be a network issue as you seem to be unable to reach the proxies themselves.

What does this command say?

traceroute www.dsodiary.com

$ traceroute www.dsodiary.com

traceroute: Warning: www.dsodiary.com has multiple addresses; using 104.27.135.181
traceroute to www.dsodiary.com (104.27.135.181), 64 hops max, 52 byte packets
1 192.168.1.253 (192.168.1.253) 4.656 ms 2.590 ms 2.481 ms
2 192.168.0.251 (192.168.0.251) 3.037 ms 3.122 ms 1.620 ms
3 static-mum-182.57.128.1.mtnl.net.in (182.57.128.1) 5.239 ms 6.261 ms 5.339 ms
4 static-mum-59.185.210.197.mtnl.net.in (59.185.210.197) 6.471 ms
static-mum-59.185.210.49.mtnl.net.in (59.185.210.49) 6.492 ms
static-mum-59.185.211.73.mtnl.net.in (59.185.211.73) 6.499 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

It seems as if it stopped within your ISPs network.

Can you open sitemeer.com? Whats the output of traceroute sitemeer.com?

Hi Sandro,

$ 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.

Cant tell you. Maybe you are on some Indian block list.

The second traceroute does get a lot farther. Based on that I’d assume it is an ISP related issue. You might want to contact your ISP about that.

It is not DNS related however.

This is a very new domain and I couldn’t find it blacklisted anywhere as such. I have raised a concern with one of the ISP.
@sandro, Really your help.

That wouldnt be domain related in this case but rather IP related.

It hosted on AWS. So blacklisted IP from AWS you mean :slight_smile: ?

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.

No, your ISP seems to block the Cloudflare’s address.

I see. Is there a way it can be changed at Cloudflare level?

I tried deleting and migrated DNS again earlier as well but I got the same DNS :stuck_out_tongue:

I am able to access other sites hosted on Cloudflare without any issue.

No, there is no standard way to change the address. You need to clarify this with the ISP.

This topic was automatically closed after 31 days. New replies are no longer allowed.