Hi,

I think I found the reason and the solution for this. I left all the
logs on stdout for a while to see if anything dodgy appeared and at some
point saw this message:

./syslog:May  7 14:16:08 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 14:28:31 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 14:30:05 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 14:37:58 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 14:39:52 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 14:41:34 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 15:29:40 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 15:29:40 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.4.4.
./syslog:May  7 15:31:31 tuxedo systemd-resolved[1434]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 15:45:41 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 15:45:41 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.4.4.
./syslog:May  7 15:49:27 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 15:51:12 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 16:08:55 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 16:08:55 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.4.4.
./syslog:May  7 16:09:10 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 16:09:11 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.4.4.
./syslog:May  7 18:00:55 tuxedo systemd-resolved[1469]: Switching to fallback 
DNS server 8.8.8.8.
./syslog:May  7 18:33:53 tuxedo systemd-resolved[1435]: Switching to fallback 
DNS server 8.8.8.8.

Which mas making no sense at all, as those DNS were changed for the
DNSWatch ones months ago (and before starting to use a VPN at all, and
are nowhere on my config files), I have no DNS servers configured aside
of the ones the VPN pushes when I connect.

So I tried this:

sudo systemd-resolve  --flush-caches

And ran an extended dns leak test on https://dnsleaktest.com/ while
connected both on the openvpn CLI and with the openvpn-network-manager-
gnome applet. Both were negative (no leaks) while they used to fail
before.

Can someone please test this too and comment?

Thanks,

J

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652525

Title:
  DNS leak in ubuntu 16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1652525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to