1 Dot DNS down

[wuder4]

1 Dot DNS is down at the moment. Is it time to panic and say: "Free internet is gone" and "Google will always get our data" and "NSA killed 1 Dot".

Or is this simply related to the new way they want to use HTTPS on DNS requests and something is broken on their end?

 

Anyway if you took Linus' tip few years back to switch DNS and now your internet is not working. Just swap your DNS to 8.8.8.8 momentarily and that should fix your problem. At least it did fix mine.

But be warned: after using 1 Dot for few years. Going back to Google's DNS is quite a big leap backwards and it DOES feel slow.

[WereCatf]

7 minutes ago, wuder4 said:

1 Dot DNS is down at the moment. Is it time to panic and say: "Free internet is gone" and "Google will always get our data" and "NSA killed 1 Dot".

Or is this simply related to the new way they want to use HTTPS on DNS requests and something is broken on their end?

Works fine on my end.

[wuder4]

When I try to ping this is the result

Pinging 1.1.1.1 with 32 bytes of data:
Reply from <my IP>: Destination host unreachable.

 

And when I try to connect to https://1.1.1.1/dns/ I get no response.

 

Could there be some issue with European server?

[Kilrah]

I have my router configured with 1. as primary and 8. as secondary, so wouldn't have seen anything.

 

But I'm in Europe and both things you say fail for you work fine here.

 

So maybe a local outage, or even just your ISP having an issue.

[WereCatf]

30 minutes ago, Kilrah said:

But I'm in Europe and both things you say fail for you work fine here.

I actually live in Finland myself, ie. the same country as OP, and it's working fine for me. So yeah, seems to be some problem with OP's ISP.

[TetraSky]

Yeah, no issues here with 1.1.1.1 either.

Quote

C:\Windows\system32>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=9ms TTL=252
Reply from 1.1.1.1: bytes=32 time=8ms TTL=252
Reply from 1.1.1.1: bytes=32 time=6ms TTL=252
Reply from 1.1.1.1: bytes=32 time=6ms TTL=252

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 9ms, Average = 7ms

 

So I'm thinking like the others that it might be a localized outage for you...

[Alex Atkin UK]

13 hours ago, Kilrah said:

I have my router configured with 1. as primary and 8. as secondary, so wouldn't have seen anything.

 

But I'm in Europe and both things you say fail for you work fine here.

 

So maybe a local outage, or even just your ISP having an issue.

Its not recommended to use different DNS providers for primary and secondary though, as it can cause some weird issues if they serve different results.

Cloudflare has 1.0.0.1 for secondary DNS.

[Kilrah]

Interesting, didn't know about that, thought secondary was only used if the primary timed out. Will try changing.