11 ms·

I wasted almost an hour trying unsuccessfully to book a cab using Uber yesterday only to realise it was 1.1.1.1 in my Private DNS which was the problem. I had

I wasted almost an hour trying unsuccessfully to book a cab using Uber yesterday only to realise it was 1.1.1.1 in my Private DNS which was the problem. I had internet access just fine (browsers) but Signal, Google Maps, Uber and Ola just wouldn't work with 1.1.1.1. Haven't gotten around to think about the reason

corint 8y ago
Me too.. Waze wasn't working and Spotify was taking ages to decide it wasn't offline. On EE in the UK if that helps?
Tsubasachan 8y ago
I use DNS66 and I have to pause it any time I use a app that involves Google.
- whalabi 8y ago
  In DNS66, in the apps tab, you can bypass the VPN by app. I think I tried this and had mixed results though. For me I only had twitter glitching at one point, but it doesn't now
fonosip 8y ago
The feature is not stable yet in this new release. Also some queries leak when your device wakes from sleep. More details here https://ba.net/adblockvpn/dnsovertls https://ba.net/adblockvpn/dnsovertls
Zizizizz 8y ago
instead of 1.1.1.1 use 1dot1dot1dot1.cloudflare-dns.com
- kfwhp 8y ago
  Wait, how are you supposed to use a host name as a DNS server?
  - ignoramous 8y ago
    DNS over HTTPS and DNS over TLS require URLs. Controversial features in that they break abstractions apart from breaking some apps too (for instance, usage of TCP, overhead of TLS/SSL handshakes, absuing HTTP etc)
  - therein 8y ago
    We heard you like to resolve domain names into IP addresses so we put your DNS provider behind an A record. This way you can resolve while you resolve.
fxfan 8y ago
Thats cloudflare not adguard. I'm surprised about your problem
IronWolve 8y ago
1.1.1.1 has issues with archive sites, had to stop using it. Cloudflare blamed the archive sites, but it works with other dns services, so I just stopped using 1.1.1.1. Interestingly at work, I found out we couldnt even route to 1.1.1.1, but gave something to the network team to work on. I too, jumped on the 1.1.1.1 bandwagon when lanched.
blacksmith_tb 8y ago
Do you have similar issues with 1.0.0.1? It seems safer for me.

corint 8y ago

Me too.. Waze wasn't working and Spotify was taking ages to decide it wasn't offline. On EE in the UK if that helps?

Tsubasachan 8y ago

I use DNS66 and I have to pause it any time I use a app that involves Google.

whalabi 8y ago
In DNS66, in the apps tab, you can bypass the VPN by app. I think I tried this and had mixed results though. For me I only had twitter glitching at one point, but it doesn't now

fonosip 8y ago

The feature is not stable yet in this new release. Also some queries leak when your device wakes from sleep. More details here https://ba.net/adblockvpn/dnsovertls https://ba.net/adblockvpn/dnsovertls

Zizizizz 8y ago

instead of 1.1.1.1 use 1dot1dot1dot1.cloudflare-dns.com

kfwhp 8y ago
Wait, how are you supposed to use a host name as a DNS server?
- ignoramous 8y ago
  DNS over HTTPS and DNS over TLS require URLs. Controversial features in that they break abstractions apart from breaking some apps too (for instance, usage of TCP, overhead of TLS/SSL handshakes, absuing HTTP etc)
- therein 8y ago
  We heard you like to resolve domain names into IP addresses so we put your DNS provider behind an A record. This way you can resolve while you resolve.

fxfan 8y ago

Thats cloudflare not adguard. I'm surprised about your problem

IronWolve 8y ago

1.1.1.1 has issues with archive sites, had to stop using it. Cloudflare blamed the archive sites, but it works with other dns services, so I just stopped using 1.1.1.1. Interestingly at work, I found out we couldnt even route to 1.1.1.1, but gave something to the network team to work on. I too, jumped on the 1.1.1.1 bandwagon when lanched.

blacksmith_tb 8y ago

Do you have similar issues with 1.0.0.1? It seems safer for me.