[Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

[Dan Streetman]

> But in the long term I guess I should move to systemd-networkd as the
> preferred way to set static ip?

that is entirely up to your preferences; ifupdown and resolvconf are
still supported, and included, and you can continue to use them.  They
are still the default way to configure the network in Debian, as far as
I know.  However, Ubuntu starting at Bionic has switched to default to
using either systemd-networkd (and system-resolved), or NetworkManager,
or both; with configuration of both/either done by netplan.  However, as
you have seen, anyone who upgrades to Bionic or later from a pre-Bionic
release will continue to use ifupdown/resolvconf.

If you're asking for what the recommended way is, then I would recommend
switching to using systemd for network management, and using netplan for
network configuration (or if you prefer, just creating systemd-networkd
conf files directly).

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken....

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
    Installed: 237-3ubuntu10.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817903/+subscriptions