Also, I'm not 100% certain the other bug is not a dupe of this one, because Yakkety. Their workarounds of restarting dnsmasq, etc. still didn't work on a 16.04 system (even restarting Network Manager didn't help - dnsmasq was still dead for *everything*), and now I'm getting issues where the domain is set proper with search domains, but I'm 'refused' from querying the domain assigned.
The DNS servers that *should* be assigned by the VPN are properly handling the requests, so I don't know what's going on and will check more later. (Falling back to local `bind9` resolver in the mean time)
Sergio,
Also, I'm not 100% certain the other bug is not a dupe of this one, because Yakkety. Their workarounds of restarting dnsmasq, etc. still didn't work on a 16.04 system (even restarting Network Manager didn't help - dnsmasq was still dead for *everything*), and now I'm getting issues where the domain is set proper with search domains, but I'm 'refused' from querying the domain assigned.
The DNS servers that *should* be assigned by the VPN are properly handling the requests, so I don't know what's going on and will check more later. (Falling back to local `bind9` resolver in the mean time)