Unable to connect to 1.1.1.1 (TELIA SE)

DNS & Network 1.1.1.1
,
#1

Hi sorry for yet another “can’t connect to 1.1.1.1” post but i’m unable to make it work

Here’s the diagnostics code

ISP : TELIA

I have never been able to connect to 1.1.1.1 yet 1.0.0.1 works.
Worth mentioning that 1.1.1.1 will work on the phone when using your app.

PS C:\WINDOWS\system32> nslookup google.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
PS C:\WINDOWS\system32> nslookup google.com 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:400f:80a::200e
216.58.207.206

PS C:\WINDOWS\system32> nslookup google.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:400f:80b::200e
172.217.20.46

PS C:\WINDOWS\system32> 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
PS C:\WINDOWS\system32> nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "ARN"
#2

That would be an indicator your ISP or your router might have hijacked the address 1.1.1.1.

Which operating system are you using?

#3

I’m using, W10 Pro.
I suspected that my ISP could have blocked it for an unknown reason, but i’m unable to contact them at these hours so I decided that I would make sure that issue was not on my end first.

#4

Can you run

tracert 1.1.1.1

in a command line and post the output here?

#5

PS C:\WINDOWS\system32> tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

#6

That would suggest the connection does not even leave your local network.

What is your hardware setup network-wise?

#7

Desktop PC > [EthernetCable] > Router > ISP
Unfortunatly the ISP doesn’t allow edits to some of the settings, and insists that I should be paying a tech to visit just to change the DNS.

#8

I presume that router is under your ISP’s control then, right?

From your traceroute it would seem as if the connection is already stopped at your router (if we rule out the possibility of your computer being involved). What model is your router?

#9

I do believe so, google do not give any results in alternative ways to gain controll of the settings.
RouterModel: Fast5370e-01

#10

The Internet does not seem to have too much on that model in regard to Cloudflare’s DNS service, but https://wuseman.github.io/SAGEMCOM-FAST-5370e-TELIA/ does seem to refer 1.1.1.1 in context with that router, so it might actually be a reserved address on that model. I cant confirm that however. It might be best to clarify this with your ISP.

1 Like
#11

Thanks for your help Sandro, i’ll consult the ISP to get a clear answer.

#13

I’ve got Sagemcom [email protected] 5370 Air / Telia Zone Hybrid router on Telia FI and it has the same issue. It uses 1.1.1.1 internally for something, Telia FI confirmed this but did not say anything about a fix.

#14