WireGuard behaviour with systemd-resolved
lanerussell at protonmail.com
Thu Sep 6 21:24:19 CEST 2018
I've noticed some concerning behaviour using WireGuard on Manjaro GNOME. When the WireGuard interface is brought up, the system starts using the DNS servers provided in the wg-client.conf file. Intermittently however, internal DNS records will resolve using their public IP addresses. Using tcpdump, I'm able to see the system is using 126.96.36.199 and 188.8.131.52 for some queries. These addresses are configured as fallback DNS servers in systemd-resolved. They were acquired via DHCP before the WireGuard interface was brought up.
Is this an issue with WireGuard, or systemd-resolved? Based on what information I'm able to find, it appears there are some big concerns with how systemd-resolved handles DNS, so I'm more inclined to think the issue lies there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the WireGuard