[Expired for resolvconf (Ubuntu) because there has been no activity for
60 days.]
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks for the quick response.
Yesterday to fix the issue, I uninstalled the resolvconf package. I
reinstalled it today, and now it is working with the correct "search"
domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
> This is also described here: https://askubuntu.com/a/1041631/326601
That describes an unrelated issue.
** Description changed:
When I rebooted my system after an update, `/etc/resolv.conf` was
symlinked to `/run/resolvconf/resolv.conf`. That file did not have my
local domain name in the
> When I rebooted my system after an update, `/etc/resolv.conf` was
> symlinked to `/run/resolvconf/resolv.conf`
That is as expected, if you have the resolvconf package installed.
> That file did not have my local domain name in the search even though
> it is supplied by the dhcp server. The sys
In particular, note that /lib/systemd/system/resolvconf-pull-
resolved.{service,path} are meant to populate /run/resolvconf/interface
/systemd-resolved using the contents of /run/systemd/resolve/stub-
resolv.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic