Le 24/07/2018 à 18:10, Tobias Brunner a écrit : Hi Vincent,
Hi Tobias, Thanks for the quick reply ! We are facing this issue too : https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705 You are not, that bug has been fixed. fixed in cosmic (5.6.2-2ubuntu1) but not in bionic (5.6.2-1ubuntu2), thus the upgrade from cosmic... `systemd-resolve --status` show the correct DNS servers in the correct order (1st got from the VPN, 2nd from the local DHCP) There you go, that already contradicts the description of the existing bug entry. yes after the applied new version of the packages, the bug is then fixed. But name resolution is still using the local DNS and even with a NX_DOMAIN error, there is no switch to the other dns server. Sounds like an issue with the systemd resolver, so you might want to report that wherever appropriate. Good news is that if I restart the service manually, the resolution is good and we can access our hosts inside vpn. I guess you mean systemd-resolved? yes it is Must I post a new issue (where please) ? Perhaps https://bugs.launchpad.net/ubuntu/+source/systemd thanks for pointing that to me I'll check and fire a bug report if needed, then post back the link here Regards, Vincent Vincent Gatignol +33 (0)6 64 61 86 97 www.braincube.com <http://braincube.com?utm_source=signature&utm_medium=e-mail&utm_campaign=lien_site_braincube> [https://cdn.mybraincube.com/mail/img.png?hash=0b2a5bda76b731d04b723764bede0815c8f23d37] <https://braincube.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=braincubeSAS>
