This isssue is not relevant to VPN connections only but also for normal workin local network. systemd-resolve and systemd-resolved stub listener are behaving differently - the stub does not accept the domain/search domains sent by DHCP. THis is really weird. Isn't the issue in domain/search domains not properly put into a dynamic /etc/resolv.conf ?
Here are few examples (domain name change to fictive example.org): 1. Test of the Domain resolving using systemd-resolve: $ systemd-resolve test test: 192.168.0.53 (test.example.org) -- Information acquired via protocol DNS in 3.0ms. -- Data is authenticated: no sob@linno ~ $ nslookup test Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find test: SERVFAIL 2. DNS resolve using the stub resolver: $ nslookup - 127.0.0.53 > test Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find test: SERVFAIL > test.example.org Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: test.example.org Address: 192.168.0.53 > 3. Example of /etc/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684854 Title: The default behaviour for search domains changed from 16.10 to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1684854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs