DNS resolution for local DNS-server might not work after iOS 14 update in Wireguard-tunnel

After updating my Apple iOS devices to iOS 14 it seems that the DNS-resolution is not working anymore, using private/local DNS-server (unbound-service on a Raspi-server) in the Wireguard-VPN-tunnel-definition.


In any case the VPN-tunnel can be established on the iOS-device, but in case I use the Safari-browser-app on the iOS-device the web-page cannot be found, it seems that the DNS-resolution does not use my defined IPv4 and IPv6 local unbound-server addresses.


If I enhance the DNS-definition in the Wireguard-app and add an official DNS like 8.8.8.8, the Safari-browser is working normal showing the data of the web-pages. In version iOS 13 and prior I do not have any problems like this.


Does this behavior is related to the change in iOS 14 introducing the DoT or DoH in the Safari-browser?

iPad, iPadOS 14

Gepostet am 22. Sept. 2020 09:22

Antworten

Ähnliche Fragen

4 Antworten

17. Dez. 2020 12:46 als Antwort auf mosensi

Yesterday I found the solution for the problem. Instead of using the real IPv4 and IPv6 addresses of the Raspberry-PI server in the Wireguard-DNS-definition, I changed this to the private-addresses of the Wireguard-server. Now the unbound-DNS-server on the Raspberry is used again.


Before I used the „real“ IP of the RasPi in the DNS-WireGuard-defintion like 192.168.170.50.


Now I am using the private Wireguard-server-address like 10.0.0.1 instead and DNS-resolution is working like in iOS version 13.



Dieser Thread wurde vom System oder dem Community-Team geschlossen. Du kannst alle Beiträge positiv bewerten, die du hilfreich findest, oder in der Community nach weiteren Antworten suchen.

DNS resolution for local DNS-server might not work after iOS 14 update in Wireguard-tunnel

Willkommen in der Apple Support Community
Ein Forum, in dem Apple-Kunden sich gegenseitig mit ihren Produkten helfen. Melde dich mit deinem Apple Account an, um Mitglied zu werden.