Again Martin, this is NOT a solution.
A fix would be something that avoids the problem from emerging in the first
place.
If stopping systemd-resolvd is a solution, that let's make sure it is NOT
enabled nor installed in 17.04 by default and let's FIX it to be the same in
16.10 if possible.
** Changed in: systemd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to connect using subdomains using
search
I'm afraid this is by design and wontfix, see
https://github.com/systemd/systemd/issues/4821#issuecomment-264995354
for details. This isn't something which we reasonably can/should change
downstream, so I suggest to direct discussions to the upstream bug.
Thanks!
** Changed in: systemd (Ubuntu)
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to connect using subdomains using
search
** Bug watch added: github.com/systemd/systemd/issues #4821
https://github.com/systemd/systemd/issues/4821
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4821
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: Confirmed =>
Same issue here, my dhcp sends "bar.name" and "name" as search domains,
systemd-resolve --status reports them correctly:
Link 1 (en)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to connect using subdomains using
search domains which are in
Same issue here, my dhcp sends "bar.name" and "name" as search domains,
systemd-resolve --status reports them correctly:
Link 1 (en)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC
Same issue here, my dhcp sends "bar.name" and "name" as search domains,
systemd-resolve --status reports them correctly:
Link 1 (en)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: allow-downgrade
DNSSEC
The workaround described above solved the issue:
$ systemctl disable systemd-resolved.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to
I am seeing the exact same behavior on my Ubuntu 16.10 (yakkety)
machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to connect using
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
12 matches
Mail list logo
