Unable to Resolve www.worldometers.info
-
@hhoong said in Unable to Resolve www.worldometers.info:
connection timed out; no servers could be reached
Well you failing to talk to cloudflare NS from that statement.. So yeah those would fail..
-
how come only this www.worldometers.info not working, very odd, i mean i donno if there is anything else that not working, so far overall everything working just fine >.<
-
Again you for whatever reason can not talk to the NS for that domain.. Do a directed query to either of those cloudflare ns
example
$ dig @collins.ns.cloudflare.com worldometers.info ; <<>> DiG 9.16.1 <<>> @collins.ns.cloudflare.com worldometers.info ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52275 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;worldometers.info. IN A ;; ANSWER SECTION: worldometers.info. 300 IN A 104.26.4.2 worldometers.info. 300 IN A 104.26.5.2 ;; Query time: 14 msec ;; SERVER: 162.159.38.226#53(162.159.38.226) ;; WHEN: Mon May 04 06:17:27 Central Daylight Time 2020 ;; MSG SIZE rcvd: 78 -
[2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: dig @collins.ns.cloudflare.com worldometers.info
; <<>> DiG 9.14.9 <<>> @collins.ns.cloudflare.com worldometers.info
; (2 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached
[2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root:anyway how do i reply in the black text box like u do ... LOL
-
Use the code box
Can you ping the IP even?
$ ping collins.ns.cloudflare.com Pinging collins.ns.cloudflare.com [162.159.38.226] with 32 bytes of data: Reply from 162.159.38.226: bytes=32 time=29ms TTL=55 Reply from 162.159.38.226: bytes=32 time=20ms TTL=55 Reply from 162.159.38.226: bytes=32 time=13ms TTL=55Those NS are the authoritative NSers for that domain - so no if you can not talk to them, then you wouldn't be able to resolve stuff they are authoritative for..
-
can ping can nslookup
odd right >.<[2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: ping collins.ns.cloudflare.com PING collins.ns.cloudflare.com (162.159.38.226): 56 data bytes 64 bytes from 162.159.38.226: icmp_seq=0 ttl=61 time=12.373 ms 64 bytes from 162.159.38.226: icmp_seq=1 ttl=61 time=11.953 ms 64 bytes from 162.159.38.226: icmp_seq=2 ttl=61 time=13.656 ms 64 bytes from 162.159.38.226: icmp_seq=3 ttl=61 time=13.199 ms 64 bytes from 162.159.38.226: icmp_seq=4 ttl=61 time=15.022 ms 64 bytes from 162.159.38.226: icmp_seq=5 ttl=61 time=13.560 ms ^C --- collins.ns.cloudflare.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 11.953/13.294/15.022/0.987 ms [2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: nslookup collins.ns.cloudflare.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: collins.ns.cloudflare.com Address: 162.159.38.226 Name: collins.ns.cloudflare.com Address: 2606:4700:50::a29f:26e2 [2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: -
Well I would say something is blocking port 53 to them then, either on your end, or the ISP or cloudflare themselves - or something between.
But if you can not query them - then you can not resolve stuff they are authoritative for.
Are you forcing traffic out a vpn connection? What part of the world are you in - is it one where they dick with dns queries?
Can you query them for something else? Say for example.
$ dig @collins.ns.cloudflare.com cloudflare.com ; <<>> DiG 9.16.1 <<>> @collins.ns.cloudflare.com cloudflare.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38819 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;cloudflare.com. IN A ;; ANSWER SECTION: cloudflare.com. 300 IN A 104.17.175.85 cloudflare.com. 300 IN A 104.17.176.85 ;; Query time: 16 msec ;; SERVER: 162.159.38.226#53(162.159.38.226) ;; WHEN: Mon May 04 06:40:32 Central Daylight Time 2020 ;; MSG SIZE rcvd: 75 -
No VPN, I'm from Malaysia,
I have 3 pfsense across 3 location, all using same telco, all 3 not working
[2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: dig @collins.ns.cloudflare.com cloudflare.com ; <<>> DiG 9.14.9 <<>> @collins.ns.cloudflare.com cloudflare.com ; (2 servers found) ;; global options: +cmd ;; connection timed out; no servers could be reached [2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: -
@hhoong said in Unable to Resolve www.worldometers.info:
all using same telco
Well that would seem to be a problem then with them.
You for whatever reason can not query them for dns - so no you wouldn't not be able to resolve anything that they are authoritative for..
Can you get to https://www.cloudflare.com/
even - maybe they don't like your ISP and are blocking them ;) Do you get a captcha when you try and access?
-
@johnpoz said in Unable to Resolve www.worldometers.info:
@hhoong said in Unable to Resolve www.worldometers.info:
all using same telco
Well that would seem to be a problem then with them.
You for whatever reason can not query them for dns - so no you wouldn't not be able to resolve anything that they are authoritative for..
Can you get to https://www.cloudflare.com/
even - maybe they don't like your ISP and are blocking them ;)
thanks for the info :)
i guess now the only way for me to able to query www.worldometers.info is to enable forwarding in my DNS resolver.
i can access to https://www.cloudflare.com/ main page,
@hhoong said in Unable to Resolve www.worldometers.info:
can ping can nslookup
odd right >.<[2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: ping collins.ns.cloudflare.com PING collins.ns.cloudflare.com (162.159.38.226): 56 data bytes 64 bytes from 162.159.38.226: icmp_seq=0 ttl=61 time=12.373 ms 64 bytes from 162.159.38.226: icmp_seq=1 ttl=61 time=11.953 ms 64 bytes from 162.159.38.226: icmp_seq=2 ttl=61 time=13.656 ms 64 bytes from 162.159.38.226: icmp_seq=3 ttl=61 time=13.199 ms 64 bytes from 162.159.38.226: icmp_seq=4 ttl=61 time=15.022 ms 64 bytes from 162.159.38.226: icmp_seq=5 ttl=61 time=13.560 ms ^C --- collins.ns.cloudflare.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 11.953/13.294/15.022/0.987 ms [2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root: nslookup collins.ns.cloudflare.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: collins.ns.cloudflare.com Address: 162.159.38.226 Name: collins.ns.cloudflare.com Address: 2606:4700:50::a29f:26e2 [2.4.5-RELEASE][admin@pfSense-Router.HuiHoong.Home]/root:i can ping and nslookup to the collins.ns.cloudflare.com as well, maybe is time for me to get a VPN
-
Could the ISP be blocking DNS to any servers but their own?
-
No since from his trace he talked to roots, and the affiliates.. He got told where to go for his domain in his trace.. He just can't seem to get there.
-
I'm not sure but overall my DNS resolver was working, i just notice this www.worldometers.info not working for now, not sure of any other that is not working.
But base on what u said, maybe all that register under @collins.ns.cloudflare.com, most likely i not able to query ... -
No you would not be able to resolve anything that you can not talk to the authoritative NS for.. When you resolve you directly talk to the authoritative NS for that domain.. If you can not get to any of them, then anything they are authoritative for would fail to resolve..
That is how resolving works.. You get the info straight from the horses mouth - if you can not talk to the horse, then yeah you going to have a bad day.
I would get with your ISP to be honest, and ask them why you can not query that NS.
-
@johnpoz said in Unable to Resolve www.worldometers.info:
No you would not be able to resolve anything that you can not talk to the authoritative NS for.. When you resolve you directly talk to the authoritative NS for that domain.. If you can not get to any of them, then anything they are authoritative for would fail to resolve..
That is how resolving works.. You get the info straight from the horses mouth - if you can not talk to the horse, then yeah you going to have a bad day.
yea ... sad,
i was so excited when i was able to not to "leak my DNS", now seem like i have to open up back to 1.1.1.1 -
Ask your ISP why you can not query that ns or the other one listed.
moura.ns.cloudflare.com
You can ping them - so you have connectivity to them, so why no query on 53?
-
@johnpoz said in Unable to Resolve www.worldometers.info:
Ask your ISP why you can not query that ns or the other one listed.
moura.ns.cloudflare.com
You can ping them - so you have connectivity to them, so why no query on 53?
i don't think they will entertain me, they would ask me to use DNS forwarder and point to them.
do pfsense resolver support DNS over SSL/TLS for outgoing to root DNS? if can, what if i enable?
i dont seem to able to find that option. -
@hhoong said in Unable to Resolve www.worldometers.info:
SSL/TLS for outgoing to root DNS?
No doesn't work that way... Every single NS on the planet would have to support tls for something like that to work.. And GAWD would be be horribly slow!!!
-
Then is sad, so for the time been i have to enable forward in my DNS resolver
until i get a VPN... hahathanks for all the help :)
-
Well if you have only found that specific one - you could prob just do a domain override to send that domain to wherever..
