Cloudflare Developers•3mo ago

DNS Propogation in one country suddenly stopped

Hello, as i said in the title, my websites are not reachable from that country anymore and when i go to a dns propagation checker, it shows that country doesnt have it, but it before days. Any idea how i can check if its a problem with me or is it just something i have to wait out. Accessing the websites in other places works fine. Im using Nginx Proxy Manager and setup my dns recods properly, as i said it works everywhere else. Any help is very appreciated!

10 Replies

Walshy•3mo ago

What's the country? What's the domain?

SaladOP•3mo ago

Server origin germany, trying to Connect from turkey. domain is "bysalad.studio" and its subdomains. also what i just tested, trying to use a vpn doesnt work, dont matter from what location or where to connect, wasnt like that before. buddy from usa cant connect now either. but i can with mobile data in germany

Walshy•3mo ago

It looks like it resolves fine globally but I see it times out Where is this hosted? It looks unproxied so not a CF issue, the IP resolves to Vodafone, not aware of them doing any hosting

SaladOP•3mo ago

my home, using nginx proxy manager, doesnt do well with CF proxy im only using CF for the dns records right now

Walshy•3mo ago

Ok so it seems like you're having issues with your own setup, I would not recommend hosting at home for so many reasons VPS' are cheap and we also have a hosting product - Pages

SaladOP•3mo ago

i mean, i can access them via domain on my home network and also using my phones mobile data outside my home network, pinging them also works. just outside of germany is a problem

Walshy•3mo ago

That still points to origin issue DNS is resolving, Cloudflare is doing what it's told to do I'd recommend seeking help from nginx proxy manager or your own ISP. I suspect the issue is the nginx setup rather than any connectivity so I'd probably start there

SaladOP•3mo ago

checked with my isp and nnginx people, all is fine. there is also some new info. there are only a few countries that can connect and some that cant. the ones that can: germany(origin) sweden netherlands the ones that cant: usa canada denmark turkey (i dont know more people in different countries to test more) isp said they didnt do anything, and they dont do things like this. npm settings all check out, and they have to cause how else would those who can connect, connect at all. the only place that i dont have full control over is CF, it has to be somewhere there

Walshy•3mo ago

The DNS is resolving, it resolves for me in the UK but times out. You can see it resolving globally here: https://dnschecker.org/#A/bysalad.studio Since it's unproxied, CF is only doing DNS. It isn't doing literally anything else. So I can't see where Cloudflare is the issue, it's doing its job.

DNS Checker

DNS Checker - DNS Check Propagation Tool

Check DNS Propagation worldwide. DNS Checker provides name server propagation check instantly. Changed nameservers so do a DNS lookup and check if DNS and nameservers have propagated.

Walshy•3mo ago

traceroute shows it's failing within germeny (and again, no cf involved since we aren't going through cf, the domain resolves fine hence us routing at all to the ip):

$ traceroute -m 32 bysalad.studio
traceroute to bysalad.studio (95.223.106.214), 32 hops max, 52 byte packets
 1  fritz.box (192.168.178.1)  3.596 ms  2.713 ms  3.205 ms
 2  lo0-0.bng5.thn-lon.zen.net.uk (51.148.77.133)  12.490 ms  13.824 ms  26.749 ms
 3  lag-15.p1.thn-lon.zen.net.uk (51.148.73.98)  11.625 ms  11.727 ms  11.873 ms
 4  ldn-b3-link.ip.twelve99.net (213.248.84.100)  10.955 ms  10.750 ms  10.918 ms
 5  ldn-bb2-link.ip.twelve99.net (62.115.122.180)  12.776 ms  11.255 ms  11.673 ms
 6  ldn-b2-link.ip.twelve99.net (62.115.122.189)  11.706 ms  14.141 ms
    ldn-b2-link.ip.twelve99.net (62.115.120.239)  13.786 ms
 7  vodafonepeering-ic-325869.ip.twelve99-cust.net (62.115.61.191)  11.389 ms  12.073 ms  17.105 ms
 8  ae31-xcr1.ltw.cw.net (195.2.10.82)  11.672 ms  11.320 ms  16.953 ms
 9  ae44-xcr1.dus.cw.net (195.2.9.41)  20.147 ms  19.427 ms  19.209 ms
10  vodafonede-gw.dus.cw.net (195.2.18.190)  20.478 ms  20.107 ms  19.306 ms
11  de-bfe18a-rd04-ae-0-0.aorta.net (84.116.191.146)  25.648 ms  27.351 ms  26.111 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *

$ traceroute -m 32 bysalad.studio
traceroute to bysalad.studio (95.223.106.214), 32 hops max, 52 byte packets
 1  fritz.box (192.168.178.1)  3.596 ms  2.713 ms  3.205 ms
 2  lo0-0.bng5.thn-lon.zen.net.uk (51.148.77.133)  12.490 ms  13.824 ms  26.749 ms
 3  lag-15.p1.thn-lon.zen.net.uk (51.148.73.98)  11.625 ms  11.727 ms  11.873 ms
 4  ldn-b3-link.ip.twelve99.net (213.248.84.100)  10.955 ms  10.750 ms  10.918 ms
 5  ldn-bb2-link.ip.twelve99.net (62.115.122.180)  12.776 ms  11.255 ms  11.673 ms
 6  ldn-b2-link.ip.twelve99.net (62.115.122.189)  11.706 ms  14.141 ms
    ldn-b2-link.ip.twelve99.net (62.115.120.239)  13.786 ms
 7  vodafonepeering-ic-325869.ip.twelve99-cust.net (62.115.61.191)  11.389 ms  12.073 ms  17.105 ms
 8  ae31-xcr1.ltw.cw.net (195.2.10.82)  11.672 ms  11.320 ms  16.953 ms
 9  ae44-xcr1.dus.cw.net (195.2.9.41)  20.147 ms  19.427 ms  19.209 ms
10  vodafonede-gw.dus.cw.net (195.2.18.190)  20.478 ms  20.107 ms  19.306 ms
11  de-bfe18a-rd04-ae-0-0.aorta.net (84.116.191.146)  25.648 ms  27.351 ms  26.111 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *

So yeah, this points more to just bad pathing existing to your house and points to your ISP Again, hosting at your house causes lots of problems (like these), I'd really recommend a VPS

Gaming

Programming

DNS Propogation in one country suddenly stopped