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

[Steve Roberts]

Thanks again for the help....

Removed resolvconf:
sudo apt remove resolvconf

reboot

as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf
and contains only:

nameserver 127.0.0.53
options edns0

BUT now I cannot connect to anything, nslookup, ping fails, etc.
$ ping google.com
ping: google.com: Temporary failure in name resolution

and
$ systemd-resolve --status
does not list any dns

So I made a guess and added DNS=192.168.2.1
to /etc/systemd/resolved.conf

$ sudo systemctl restart systemd-resolved

now
$ systemd-resolve --status
lists dns as 192.168.2.1

and all is good...

Additional info:
I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was specified in
/etc/network/interfaces

Seems resolvconf was detecting this and adding the dns to resolv.conf,
but systemd-resolve is not looking or detecting ?

So it seems to that the issue is really that systemd-resolve is adding
the options to resolv.conf when it shouldn't interfere because
resolvconf is in charge of it OR that systemd-resolve isn't checking
/etc/network/interfaces for dns-nameservers....

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

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