> PS: short domains also don't work. Only FQDNs.
Fixed by changing:
hosts: files mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns
to
hosts: files mdns4_minimal [NOTFOUND=return] dns
--
You received this bug notification because you are a member of Desktop
I added search domains in '/etc/resolvconf/resolv.conf.d/base'. Now, I
have at least named access to servers outside of our internal network.
Is there some checkbox in settings to enable searchdomains coming from
dhcp?
PS: short domains also don't work. Only FQDNs.
--
You received this bug
I struggled with this long enough and took some notes about a workaround
here: https://thealarmclocksixam.com/2017/08/08/dns-configuration-with-
vpns-and-ubuntu-17-04-working-again/
I hope that this can help someone else as well.
--
You received this bug notification because you are a member of
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
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
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
*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Kubuntu 17.04: openvpn
If “use this connection only for resources on its network” is checked,
"systemd-resolve --status" shows "~" before the domain name as ThyMythos said.
And adding the correct domain on the options have not effect, only takes the
domain pushed by vpn server prefixed with
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
9 matches
Mail list logo
