I still see this in 20.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717995
Title:
extra domains not removed from resolv.conf when VPN disconnects
Status in systemd
Still have it in Ubuntu 19.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717995
Title:
extra domains not removed from resolv.conf when VPN disconnects
Status in
I have had the same exact problem since I have upgraded to 17.10. In my
case it does not even involve the VPN. When I come back from work, if I
had suspended the laptop without restarting it, then I cannot connect to
the computers from work.
If I restart resolvconf with:
$ sudo
The fix is incorporated in 236, but the systemd developer suggests the
fix could be backported to 234. What version of systemd will be in
bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It seems this systemd bug is related and is supposed to be fixed. I still
experience the problem however:
https://github.com/systemd/systemd/issues/7305
** Bug watch added: github.com/systemd/systemd/issues #7305
https://github.com/systemd/systemd/issues/7305
--
You received this bug
Same for me. I really don't understand how /etc/resolv.conf should be
managed in Ubuntu 17.04. I have the setup described in comment #7. I
tried to have only network-manager manage /etc/resolv.conf, but then I
loose name resolution in containers.
I think we should open a new bug report, as this
I still have this problem. When I disconnect from a VPN, the various
resolv files retain a search line and DNS lookup fails for the domain
associated with the VPN (in this case, my university). Luckily, this is
fairly easy to work around (I no longer reboot to try to fix my
network). Did I miss
This bug was fixed in the package systemd - 234-2ubuntu12
---
systemd (234-2ubuntu12) artful; urgency=medium
[ Dimitri John Ledkov ]
* debian/rules: do not strip test-copy.
This insures test-copy is large enough for test-copy tests to pass.
(LP: #1721203)
[ Michael
I'm experiencing this same issue.
A workaround that works for me is to remove my vpn domain from
/etc/resolv.conf. The last line of this file looks as follows after a
successful VPN connection:
search Home myvpndomain
where the last term is the domain of my vpn (vpn.bla.com). The workaround is
Great, let me know if you want me to try anything out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717995
Title:
extra domains not removed from resolv.conf when VPN
I believe I have a fix for this. There is a feedback loop which was not
closed, with resolved re-reading /etc/resolv.conf and thus DNS domains
leaking from per-link scope, into the global scope, and staying there,
even when the link is dead / gone.
** Changed in: systemd (Ubuntu)
Status:
I wonder if the issue has anything to do with the fact that the VPN
creates a new network link that disappears when the VPN goes down - note
that the purestorage.com domains are listed for tun0 when the VPN is up.
When I turn off the VPN, tun0 disappears but the purestorage.com domains
stay in the
$ systemd-resolve webvpn.purestorage.com
webvpn.purestorage.com: resolve call failed: No appropriate name servers or
networks for name found
$ systemd-resolve --status
Global
DNS Domain: home.digitalvampire.org
purestorage.com
Could you paste the output from
$ systemd-resolved --status
when the system is in a bad state? That is, system mentions the domains in
/etc/resolv.conf when it should not have.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance:
14 matches
Mail list logo
