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.
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..
-
@johnpoz
hmm, let me try ... -
But if you can not talk to those specific ns for cloudflare, its possible you can not talk to others. Also I would "assume" that those ns are used for more than just that specific domain.. So there could be others that you can not resolve - that you have just not found yet.
So while a conditional forward would allow you to resolve this specific domain, you could have things that don't resolve later that you have just not run across yet. So it would be a wack-a-mole game.. The root of the problem is you can not talk to those NS for whatever reason via dns query.
-
This one :
@johnpoz said in Unable to Resolve www.worldometers.info:
moura.ns.cloudflare.com
and it's brother collins.ns.cloudflare.com are most probably servers or VPS hosted by cloudflare. To me, it like they are dedicated servers that have as a role : a name server.
But they are managed by a private person, because :
Double; identical A records are returned.
Both name servers are in the same AS : that a DNS bad practice.
"cloudfare" should never done that.
And private person means : a trigger happy server with fail2ban, DNSBL software ....This ll boils down to : you got yourself probably blacklisted - or worse, your (ISP) WAN IP is on some blacklist, used by the guy who operates worldoyyyymeters.info.
edit : I just had a look at what that site www.worldoyyyyymeters.info is ... a Corona counter ...
-
Where do you see they return the same IP?
;; ANSWER SECTION:
collins.ns.cloudflare.com. 86383 IN A 162.159.38.226;; ANSWER SECTION:
moura.ns.cloudflare.com. 86375 IN A 162.159.44.217They are are in different networks..
And that network is owned by cloudflare.. And while they are part of the same block, there is nothing wrong with having 2 ns in the same AS.. They just shouldn't be on the same network.. You could have same AS all over the globe, so there is no reason why they couldn't be in the same AS.. In a perfect world sure - you would put your NS in completely different AS, I agree.
But sure if those are hosted by cloudflare for someone, if that someone runs that NS, then sure they could of blocked his IP or block.. Its its possible cloudflare is actually blocking his IP.. very possible!
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.8, 24.11 -
@johnpoz said in Unable to Resolve www.worldometers.info:
Where do you see they return the same IP?
;; ANSWER SECTION:
collins.ns.cloudflare.com. 86383 IN A 162.159.38.226;; ANSWER SECTION:
moura.ns.cloudflare.com. 86375 IN A 162.159.44.217They are are in different networks..
And that network is owned by cloudflare.. And while they are part of the same block, there is nothing wrong with having 2 ns in the same AS.. They just shouldn't be on the same network.. You could have same AS all over the globe, so there is no reason why they couldn't be in the same AS.. In a perfect world sure - you would put your NS in completely different AS, I agree.
But sure if those are hosted by cloudflare for someone, if that someone runs that NS, then sure they could of blocked his IP or block.. Its its possible cloudflare is actually blocking his IP.. very possible!
y they wanna block me... I'm so sad :(
-
@johnpoz said in Unable to Resolve www.worldoyyyymeters.info:
Where do you see they return the same IP?
Here :
AS : do something like https://www.zonemaster.net/domain_check
@johnpoz said in Unable to Resolve www.worldoyyyymeters.info:
there is nothing wrong with having 2 ns in the same AS
It will work just fine. It just not good practice. Most domain - name - root server tester will tell you this.
@johnpoz said in Unable to Resolve www.worldoyyyymeters.info:
And that network is owned by cloudflare.
The network, yes. These name server : I guess probably not - as said, some rented dedicated server.
-
The hard part is figure out why you can not get there, clearly you can ping it.. But dns is being blocked somewhere between you and them.. Where that is happening is the question.
-
That is the Site, not the NS for the domain.
Look as something major player - and their NS are quite often on the same AS, just different network blocks - most likely in different regions of the world.
We have same AS, and just different networks under the AS are advertised out of different locations..
Now a days many of the IPs used for NS are just going to be anycast anyway. Look at google dns for example 8.8.8.8 and 8.8.4.4, both are in the same AS 15169
-
@hhoong said in Unable to Resolve www.worldometers.info:
y they wanna block me... I'm so sad :(
What about the solution that worked well for the last couple of thousand of centuries : ask them ? https://www.worldoxxxxxmeters.info/contact/
-
@Gertjan said in Unable to Resolve www.worldometers.info:
@hhoong said in Unable to Resolve www.worldometers.info:
y they wanna block me... I'm so sad :(
What about the solution that worked well for the last couple of thousand of centuries : ask them ? https://www.worldometers.info/contact/
actually not My IP that got blocked.
i have 3 pfSense over 3 different location, but all same ISP, maybe the ISP been blocked?
maybe i can ask https://www.worldometers.info/contact/ as u suggested :) -
@hhoong said in Unable to Resolve www.worldometers.info:
actually not My IP that got blocked.
Still, not a real problem.
Thee letter solution : VPN ;)
( to get an IP that will work ) -
You can traceroute to 104.26.5.2 and 104.26.4.2 all right?
I suppose in the meantime you could add the IPs to /etc/hosts...no? Or is that what Host Overrides are for?
Can't hit the target by using the IP in the URL.
Just my 2 cents. Ignore as needed. :)
-
@provels said in Unable to Resolve www.worldometers.info:
Or is that what Host Overrides are for?
Bringing the name resolution to home would work.
The IP itself, the A record, is also not accessible for @hhoong.There is some progress on the site : it's loaded up to the ceiling with Google adds now.
I had to stop pfBlocker to make it visible again.
It's probably not even a dedicated web server, but a shared web server .... just some private guy who build it's own site, as we all do or have done.
@hhoong : this site is just a small java counter with some html. Many other sites showing the same info exist, without obliteration the viewer with WoW publicity.
