[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-06-08 Thread ThyMythos
As a workaround you can do: MY_DOMAIN="abc.org" LINKS=`busctl tree --list org.freedesktop.resolve1 | grep link/_` for L in $LINKS; do busctl get-property org.freedesktop.resolve1 $L org.freedesktop.resolve1.Link Domains \ | grep -q $MY_DOMAIN \ && sudo busctl call org.free

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-26 Thread ThyMythos
Seems this lines of code are responsible: src/dns/nm-dns-systemd-resolved.c: static void add_domain (GVariantBuilder *domains, const char *domain, gboolean never_default) { /* If this link is never the default (e.g. only used for resources on this * netwo

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-21 Thread ThyMythos
I did some more tests. Using "dns-search=my.domain" and "ignore-auto- dns=true" actually works for wifi connections. For VPN (vpnc) is does not work. The tool "systemd-resolve --status" still shows a tilda before the domain name ("DNS Domain: ~my.domain" instead of "DNS Domain: my.domain") and the

[Touch-packages] [Bug 1684854] [NEW] The default behaviour for search domains changed from 16.10 to 17.04

2017-04-20 Thread ThyMythos
Public bug reported: Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default behaviour for search domains changed. By default systemd-resolved does not use the domain supplied by DHCP as a search domain. So network-manager should at least have an option to tell systemd- networkd to c