AdguardTeam / AdguardTeam/AdGuardDNS

AdGuard encrypted DNS using iOS/macOS config profiles fails to reconnect after using a VPN

Aberta
#125 5 comentários 0 reações 1 responsável Reivindicada por @Chinaski1 Ver no GitHub
Priority: P4
Linguagem predominante
Go
Estrelas
952
Forks
82
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

When using AdGuardDNS on iPhone, iPad or Mac using the new encrypted DNS configuration profiles (available to download on AdGuard's website [here](https://adguard.com/en/blog/encrypted-dns-ios-14.html)), after connecting and disconnecting to/from a VPN service, the device reverts back to using the default ISP DNS, despite the Settings app still showing AdGuard as selected. This is occurring on iOS 14.2, iPadOS 14.2 and macOS Big Sur 11.0.1 (the latest public versions of all 3), and the only way to get the device to use AdGuardDNS again seems to be to reboot.

Here is how I tested the issue:

1. Install AdGuard DNS profile (also tested with NextDNS)
2. Select it as the DNS provider in settings (restart was required on iPhone for this to take effect, but strangely not on iPad or Mac)
3. Open ProtonVPN and start a connection (also tested with Windscribe)
4. Terminate VPN
5. Settings app still shows AdGuard DNS as active but DNSLeakTest.com shows my ISP's DNS servers
6. Only fix is to restart the device

There is a Reddit thread discussing this bug on r/AdGuard, available [here](https://www.reddit.com/r/Adguard/comments/k0pufu/dns_problems_on_macos_big_sur_and_ios_14_not_sure/).

Since this affects both AdGuard and NextDNS, it seems this is probably a bug with the OS, and not an issue on AdGuard's part - but I thought I would post it here just to make the team aware that it exists. I have reported the bug to Apple via their Feedback Assistant webpage, and I suggest others do the same.

Strangely, last night, the bug seemed to temporarily disappear since I was able to connect to ProtonVPN on my iPhone and iPad, and then disconnect and go straight back to using AdGuardDNS as expected. However, I then tested this on my Mac and found that the bug was very much still there, and then tried Windscribe VPN on my iPhone and iPad and once again, upon termination of the VPN, my devices reverted to using my ISP's DNS server.

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.