[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
Martin Pecka
peci1 at seznam.cz
Tue May 7 09:28:07 UTC 2019
I successfully work around this issue by the steps described at
https://askubuntu.com/a/907249/153828 :
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service
sudo systemctl stop systemd-resolved
Then put the following line in the [main] section of your
/etc/NetworkManager/NetworkManager.conf:
dns=default
Delete the symlink /etc/resolv.conf
rm /etc/resolv.conf
Restart network-manager
sudo service network-manager restart
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1699660
Title:
systemd-resolve breaks resolution of local network hostnames
Status in systemd package in Ubuntu:
Confirmed
Bug description:
After upgrading to Ubuntu 17.04 (zesty), resolution of my local
network's host names is completely broken. Apparently the upgrade
replaced my existing resolver with systemd-resolve, which deliberately
refuses to pass "single-label" domain names to my domain name server.
That is the server where all my network's host names are kept, so I
can no longer resolve any of them.
Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware.
https://github.com/systemd/systemd/issues/2514#issuecomment-179203186
Would someone sensible please put a stop to this forced breakage
during upgrade, and advise on how to fix it now that the damage has
been done?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions
More information about the foundations-bugs
mailing list