[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames

[ironstorm]

Thanks Martin, your solution to disable systemd-resolve allowed me to
finally resolve hosts on my local network again...  I was using a
temporary workaround of replacing "echo 'nameserver 192.168.1.1' >
/etc/resolv.conf", however that doesn't survive reboots.

This issue should be addressed by Ubuntu devs, systemd is pretty
seriously f-ing up a basic form of usability in being able to resolve
machines (and devices) by name on a local home network.

-- 
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