It's dnsmasq that keep on using the LAN DNS instead 2 others DNS have already been defined for the VPN tunnel nov. 28 15:32:14 callisto dnsmasq[1432]: configuration des serveurs amonts à partir de DBus nov. 28 15:32:14 callisto dnsmasq[1432]: utilise le serveur de nom 192.168.0.254#53 nov. 28 15:32:14 callisto NetworkManager[12918]: Writing DNS information to /sbin/resolvconf nov. 28 15:32:14 callisto dnsmasq[1432]: configuration des serveurs amonts à partir de DBus nov. 28 15:32:14 callisto NetworkManager[12918]: (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] nov. 28 15:32:14 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_GLOBAL nov. 28 15:32:14 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_SITE nov. 28 15:32:14 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_GLOBAL nov. 28 15:32:14 callisto NetworkManager[12918]: Writing DNS information to /sbin/resolvconf nov. 28 15:32:14 callisto dnsmasq[1432]: configuration des serveurs amonts à partir de DBus nov. 28 15:32:14 callisto dnsmasq[1432]: utilise le serveur de nom 192.168.0.254#53 nov. 28 15:32:14 callisto NetworkManager[12918]: (eth0): Activation: successful, device activated. nov. 28 15:32:15 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_LOCAL nov. 28 15:32:15 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_GLOBAL nov. 28 15:32:15 callisto NetworkManager[12918]: Writing DNS information to /sbin/resolvconf nov. 28 15:32:15 callisto dnsmasq[1432]: configuration des serveurs amonts à partir de DBus nov. 28 15:32:15 callisto dnsmasq[1432]: utilise le serveur de nom 209.222.18.222#53 nov. 28 15:32:15 callisto dnsmasq[1432]: utilise le serveur de nom 209.222.18.218#53 nov. 28 15:32:15 callisto NetworkManager[12918]: keyfile: add connection in-memory (xcvwcvwcvwcvwcvwcvwcv") nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: unavailable -> disconnected (reason 'connection-assumed') [ nov. 28 15:32:15 callisto NetworkManager[12918]: Device 'tun0' has no connection; scheduling activate_check in 0 seconds. nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): Activation: starting connection 'tun0' (bfghfghdghdfhdfghdfghdfhdfh) nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: disconnected -> prepare (reason 'none') [30 40 0] nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: prepare -> config (reason 'none') [40 50 0] nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: config -> ip-config (reason 'none') [50 70 0] nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): device state change: secondaries -> activated (reason 'none') [90 100 0] nov. 28 15:32:15 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_LOCAL nov. 28 15:32:15 callisto NetworkManager[12918]: NetworkManager state is now CONNECTED_GLOBAL nov. 28 15:32:15 callisto NetworkManager[12918]: Policy set 'tun0' (tun0) as default for IPv4 routing and DNS. nov. 28 15:32:15 callisto NetworkManager[12918]: Writing DNS information to /sbin/resolvconf nov. 28 15:32:15 callisto dnsmasq[1432]: configuration des serveurs amonts à partir de DBus nov. 28 15:32:15 callisto dnsmasq[1432]: utilise le serveur de nom 209.222.18.222#53 nov. 28 15:32:15 callisto dnsmasq[1432]: utilise le serveur de nom 209.222.18.218#53 nov. 28 15:32:15 callisto dnsmasq[1432]: utilise le serveur de nom 192.168.0.254#53 nov. 28 15:32:15 callisto NetworkManager[12918]: (tun0): Activation: successful, device activated.