Unable to Resolve www.worldometers.info

Gertjan

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

johnpoz

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.

johnpoz

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

Gertjan

@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/

hhoong

@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 :)

Gertjan

@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 )

provels

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. :)

Gertjan

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

provels

@Gertjan said in Unable to Resolve www.worldometers.info:

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.

Wow, didn't know. Never seen an ad there. Thanks, pfB!

Gertjan

@provels said in Unable to Resolve www.worldometers.info:

Never seen an ad there. Thanks, pfB!

Shut down pfblocker and check for yourself.
80 % of the page are screaming adds.

edit : Nothing against adds .. but now I'm going to edit all my messages above to nuke the URL's. No need to bring that site more revenue for the cause it seems to represent.

edit2: @chpalmer is right after all ?

johnpoz

The destination doesn't really matter with this problem.. It could be a site for midget p0rn - doesn't matter what the site is..

Doesn't matter what the IP that returned is, or even if he can get to that IP.

The problem here is he can not resolve the name, and can not talk to clouldflare ns.. That are listed as the authoritative NS for this domain.

He can not query

;; 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.217

Doesn't matter what he is trying to resolve, he can not resolve anything from either of those. He should be able to resolve their own names from them for example.

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @162.159.38.226 collins.ns.cloudflare.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31172
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;collins.ns.cloudflare.com.     IN      A

;; ANSWER SECTION:
collins.ns.cloudflare.com. 86400 IN     A       162.159.38.226

;; Query time: 27 msec
;; SERVER: 162.159.38.226#53(162.159.38.226)
;; WHEN: Wed May 06 08:58:09 CDT 2020
;; MSG SIZE  rcvd: 70

Who cares what the site he is trying to resolve is full of ads, etc... That doesn't matter in what the issue is. The owner of that server could be blocking him, doesn't matter since he can not resolve it anyway..

Gertjan

I fully agree, understand etc.

What the site world ... info shows isn't the issue here - it's not for me to somehow judge that.

I presume it's not even the site admin who's blocking the access to the (his) name servers here, but cloudfare itself.

As said : a VPN would be a solution here.

johnpoz

It could be his ISP, it could be cloudflare - don't know where the block is happening.. Or if not a block on purpose but some weird shit his isp is doing with dns queries, etc. etc..

He asked why he can not resolve that - the answer to that is he can not talk to the authoritative ns on port 53, he gets no answer.. just time out..

Since he is coming from 3 different sites, but the same ISP.. We still do not know if something his ISP is doing, something clouldflare is doing, etc.

He really should contact his ISP and ask them why he can not query these 2 name servers..

chpalmer

@johnpoz said in Unable to Resolve www.worldometers.info:

The destination doesn't really matter with this problem.. It could be a site for midget p0rn - doesn't matter what the site is..

Unless its someone trying to get people to look at propaganda page. Click bate. That is a political page trying to push that the world is overpopulated and that governments should do something.

My network for some reason cannot reach this site.. https://www.improbable.com/teach/lessons2002/people-in-texas.html Maybe related..

( I know there would not be enough room to move around before you start typing)

johnpoz

Again its not about you getting to the site or not - its the fact of resolving it... That site is also cloudflare dns..

Can you not resolve it?

$ dig www.improbable.com

; <<>> DiG 9.16.1 <<>> www.improbable.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4181
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.improbable.com.            IN      A

;; ANSWER SECTION:
www.improbable.com.     3600    IN      A       104.27.163.33
www.improbable.com.     3600    IN      A       104.27.162.33

;; Query time: 71 msec
;; SERVER: 192.168.3.10#53(192.168.3.10)
;; WHEN: Wed May 06 12:52:48 Central Daylight Time 2020
;; MSG SIZE  rcvd: 79

here is trace

$ dig www.improbable.com +trace

; <<>> DiG 9.16.1 <<>> www.improbable.com +trace
;; global options: +cmd
.                       81565   IN      NS      h.root-servers.net.
.                       81565   IN      NS      b.root-servers.net.
.                       81565   IN      NS      j.root-servers.net.
.                       81565   IN      NS      e.root-servers.net.
.                       81565   IN      NS      c.root-servers.net.
.                       81565   IN      NS      d.root-servers.net.
.                       81565   IN      NS      m.root-servers.net.
.                       81565   IN      NS      g.root-servers.net.
.                       81565   IN      NS      a.root-servers.net.
.                       81565   IN      NS      l.root-servers.net.
.                       81565   IN      NS      i.root-servers.net.
.                       81565   IN      NS      f.root-servers.net.
.                       81565   IN      NS      k.root-servers.net.
.                       81565   IN      RRSIG   NS 8 0 518400 20200519050000 20200506040000 48903 . b3rDX8hw+NlEeGXwx0uYMKtwjStmSBgr6EdkvQxqhrTHRpqyfywF0Du6 5Vy0XT9nq54eqDfK1AvD7q8rH/qc+mpd5TQoQdkpCW0wad1tZsnnwwFr VUq7H+LM3FBXc024sZG6ha7MZpdm3rDIEF1QpVjgbWpfEqEqIh9qUzlG gnKm8c9ZJLDZ8GV8bAO42miSRjaMgipCcQkZ6FZru8WFo7XiGJ+lUkpQ OIBLMm55LR5zwF4/0+Zu+fXZIay9+9S2CbPwscWqfZnJUzBCXt/Xsjdq u97c5MM2hV3wmlYRlsubnKER5RDZYJDSsKwipJekfsgo6nGo5TD2PWM8 aT82pg==
;; Received 525 bytes from 192.168.3.10#53(192.168.3.10) in 3 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    86400   IN      DS      30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.                    86400   IN      RRSIG   DS 8 1 86400 20200519170000 20200506160000 48903 . YyraVh9G5c5nXgKNPGsh72KnhrzpuZ5Hn55AQ7QT60SQbfxPFYN1y3D0 iySMImGx6EWg7rpxwsq/XrCyE415G2SfFzSJu27/PfgI5itPmlDeaksK DCiPDAh24ps5F8dA1gs5bEhXg6v1I4Bs9utYjVgZ//4DdlA6hUsOK41t QgWa2PDNJncShftRKwxKZbFq3b1CTvpFywIQz0WHCDfaqR1wN+wYxPrK XzpHN4Pht+9j/faQmdTBUZchCQG0/ki+Xv1ZIQ2FsfKfPK2Q+vlwYoa3 T6P3IKu6R/iM+i7i3WEkTb7mX+HC3/0YQqQotDQ51kcH0sOkzs40L+3P m03r/w==
;; Received 1178 bytes from 199.7.91.13#53(d.root-servers.net) in 12 ms

improbable.com.         172800  IN      NS      lee.ns.cloudflare.com.
improbable.com.         172800  IN      NS      edna.ns.cloudflare.com.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20200513044951 20200506033951 39844 com. DQ9LaY7nv4abiSkEn0gpiP0cQ8J7yqT4l29DPEUyTure4dT/cQOGGhB4 YaB6r/2IAy0Q32WN2JIPrBQZWYFans5vdqZKOE0bT5WIOCK3TFqfmpKy wcaRIcAqloo2ucXB5WSk30r4+ep3DgkfgQyAmgDfJWM0jMEMPxRYhm3l DBVkbvRe4un6nc1i07mz7d1i25O8nmx24r929EcMKPlF4w== 3I65V3ONV364ETJ2N1O9QUJPSL5CIF78.com. 86400 IN NSEC3 1 1 0 - 3I672DQ9VK3GG4PH2A6ALH81124LCHFC NS DS RRSIG
3I65V3ONV364ETJ2N1O9QUJPSL5CIF78.com. 86400 IN RRSIG NSEC3 8 2 86400 20200513052416 20200506041416 39844 com. jBWZ6lII936oHQstMrhhjdBd4s9htotlcd/OoB7/uJqZKMNcvU8kgrc7 Pq56BylJdf3IPPCQoNQB46scFOxQDI2HHgU8dQVnNe5yVvVjL6nk4hrY qPZ+NQlk8DP7ej5fEdbLB01zYe9iiAvAHgE1K7k1ygn4kDZXQmkM2v/N P+Jb2o6TRM4NeatDghxTmh2ST1XHP/zd8Vv2OoQASH4oJQ== ;; Received 735 bytes from 192.5.6.30#53(a.gtld-servers.net) in 31 ms

www.improbable.com.     300     IN      A       104.27.162.33
www.improbable.com.     300     IN      A       104.27.163.33
;; Received 79 bytes from 173.245.58.109#53(edna.ns.cloudflare.com) in 25 ms

The site could be utter crap.. That is not the point.. There is one thing if he was using dns that did "filtering" and blocked it because it had xyz, or whatever.. But he is resolving, and trying to talk to the authoritative ns for that domain. Its not the ISP place to filter dns, unless they want to do that via their dns servers... He is trying to talk from his IP to some IP on the internet on port 53... Not his isp place to filter that, if that is what they are doing because they don't like whatever sites that NS my resolve..