I can confirm the issue, but I'm still working on getting things
clarified as to how exactly we should handle /etc/hosts. It's starting
to be clear that the changes should be "as little as possible" and "only
if it's not already set by the admin", but this still causes issues
where, like here I assume, NetworkManager is expected to handle
*everything* in the network connection, including setting the proper
FQDN for the current connection it possibly gets from DHCP.
Note that with this feature complete, you could get into weird
issues/weird domain names in /etc/hosts when you log on to public
wireless access points, for example.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659817
Title:
NetworkManage does not set domain in /etc/hosts on DHCP connections
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
