1.1.1.1 still not working from Telecom Argentina


#1

1.0.0.1 works just fine.

1.1.1.1 on the other hand gives “connection refused” on the browser. Responds to pings just fine but it is unreachable as DNS.


#2

Can you run through these few steps and post the results here?


#3

Here are the results:

NAME RESOLUTION

nslookup tecnogaming.com 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

nslookup tecnogaming.com 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

Non-authoritative answer:
Name: tecnogaming.com
Address: 192.254.76.124

nslookup -class=chaos -type=txt id.server 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

nslookup -type=txt whoami.cloudflare.com ns3.cloudflare.com
Server: ns3.cloudflare.com
Address: 162.159.7.226

whoami.cloudflare.com text =

    "190.228.76.41"

ROUTING

tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 4 ms 3 ms 10.111.111.2
3 5 ms 4 ms 4 ms 10.33.20.3
4 5 ms 5 ms 4 ms 190.228.80.252
5 11 ms 10 ms 11 ms 190.228.80.254
6 19 ms 20 ms 18 ms host85.190-226-174.telecom.net.ar [190.226.174.85]
7 35 ms 35 ms 33 ms host32.181-96-114.telecom.net.ar [181.96.114.32]
8 42 ms 45 ms 93 ms host156.181-88-80.telecom.net.ar [181.88.80.156]
9 36 ms 36 ms 36 ms host45.200-3-81.telecom.net.ar [200.3.81.45]
10 33 ms 33 ms 32 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.

tracert 1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 5 ms 5 ms 10.111.111.2
3 5 ms 4 ms 5 ms 10.33.20.3
4 5 ms 5 ms 4 ms 190.228.80.252
5 12 ms 10 ms 12 ms 190.228.80.254
6 21 ms 23 ms 20 ms host85.190-226-174.telecom.net.ar [190.226.174.85]
7 26 ms 25 ms 26 ms host36.181-96-114.telecom.net.ar [181.96.114.36]
8 44 ms 40 ms 38 ms host177.181-88-80.telecom.net.ar [181.88.80.177]
9 37 ms 39 ms 39 ms host210.181-88-80.telecom.net.ar [181.88.80.210]
10 46 ms 39 ms 37 ms et5-1-2.baires5.bai.seabone.net [185.70.203.48]
11 35 ms 35 ms 34 ms et4-3-0.baires3.bai.seabone.net [185.70.203.11]
12 56 ms 37 ms 38 ms cloudflare.baires3.bai.seabone.net [185.70.203.71]
13 36 ms 35 ms 36 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.

BONUS POINTS

nslookup -class=chaos -type=txt id.server 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "eze01"

nslookup -vc -class=chaos -type=txt id.server 1.1.1.1
Server: UnKnown
Address: 1.1.1.1

*** UnKnown can’t find id.server: Unspecified error

nslookup -vc -class=chaos -type=txt id.server 1.0.0.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "eze01"

I hope this helps solve the issue.


#4

Ohh you juicy, juicy 1.1.1.1 :wink:

Does Telecom Argentina really hijack the IP at this point?


#5

Let me try with Level3 and report back


#6

Our backbone doesn’t know the route to 200.3.81.45:

[email protected]: traceroute 200.3.81.45
traceroute to 200.3.81.45 (200.3.81.45), 30 hops max, 60 byte packets
1 172.30.0.1 (172.30.0.1) 0.529 ms 0.841 ms 1.138 ms
2 62.xxx.xxx.xxx (62.xxx.xxx.xxx) 4.572 ms 4.583 ms 4.608 ms
3 gi7-2…xxxxxxxxxxxx (212.x.xxxx.xxx) 5.024 ms !N * *
[email protected]:~$

Either not advertised, misconfigured or 1.1.1.1 was in fact hijacked / sinkholed for whatever the reason is

Same from my ADSL at home:

C:\Users\Mark>tracert 200.3.81.45

Routenverfolgung zu host45.200-3-81.telecom.net.ar [200.3.81.45]
über maximal 30 Hops:

1 3 ms 2 ms 9 ms fritz.box [192.168.178.1]
2 9 ms 10 ms 9 ms 217.0.xxx.9
3 10 ms 13 ms 12 ms 217.0.xxx.54
4 * * * Zeitüberschreitung der Anforderung.
5 * * * Zeitüberschreitung der Anforderung.
6 * * * Zeitüberschreitung der Anforderung.
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.
18 * * * Zeitüberschreitung der Anforderung.
19 * * * Zeitüberschreitung der Anforderung.
20 * * * Zeitüberschreitung der Anforderung.
21 * * * Zeitüberschreitung der Anforderung.
22 * * * Zeitüberschreitung der Anforderung.
23 * * * Zeitüberschreitung der Anforderung.
24 * * * Zeitüberschreitung der Anforderung.
25 * * * Zeitüberschreitung der Anforderung.
26 * * * Zeitüberschreitung der Anforderung.
27 * * * Zeitüberschreitung der Anforderung.
28 * * * Zeitüberschreitung der Anforderung.
29 * * * Zeitüberschreitung der Anforderung.
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Users\Mark>


#7

Since 1.0.0.1 is working on all ISP i’ll concentrate on 1.1.1.1

This is from a public free ISP on our providence (Level3)

nslookup tecnogaming.com 1.1.1.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1

Non-authoritative answer:
Name: tecnogaming.com
Address: 192.254.76.124

tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 4 ms <1 ms <1 ms 192.168.0.1
2 15 ms 13 ms 9 ms 20.0.0.1
3 22 ms 7 ms 17 ms 10.13.172.129
4 564 ms 21 ms 11 ms 10.16.2.97
5 149 ms 78 ms 9 ms 10.16.2.81
6 562 ms 11 ms 18 ms 10.16.2.73
7 177 ms 68 ms 29 ms 10.16.2.65
8 * * * Request timed out.
9 78 ms 23 ms 68 ms 172.30.13.1
10 777 ms 199 ms 213 ms 192-169-30-26.dsl.beggstelco.net [192.169.30.26]
11 34 ms 57 ms 25 ms 146.82.32.221
12 58 ms 47 ms 45 ms 201-234-128-45.static.impsat.net.ar [201.234.128.45]
13 56 ms 65 ms 77 ms ae1.ar3.eze1.gblx.net [67.16.146.186]
14 59 ms 76 ms 70 ms 208.51.134.130
15 200 ms 167 ms 75 ms cloudflare.baires3.bai.seabone.net [185.70.203.71]
16 55 ms 125 ms 56 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.

nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "eze01"

So it seems it’s Telecom Argentina the responsible for this timeout as Level3 appears to be working.


#8

To be fair, I cant reach any of the host*.telecom.net.ar hosts in the traceroute, but what caught my attention was the fact how close 1.1.1.1 is supposed to their network, when 1.0.0.1 goes via seabone.net.

To me this looks like a classic misrouting to an actual machine (notice that it actually responds to the traceroute) - be it intentionally or not.

@tecnogaming, can you adjust the title? It doesnt seem to be all of Argentina not liking Cloudflare, only TA :slight_smile:


#9

Indeed. Adjusted.

Any idea how can we fix this?. I am in contact with my ISP and I could contact Telecom through them but I don’t know how to request a fix for this.


#10

You could certainly try contacting them, but knowing telecoms I am not sure if a complaint from a single person would be heard (particularly within any reasonable amount of time).

Your ISP should (hopefully) have the right contacts (and interest to get this fixed :wink: ), alternatively maybe Cloudflare can use their channels :slight_smile: @cscharff


#11

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