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

[Steve Roberts]

Thanks for the attention to this:

DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by
isp)

typical sites: planthealth.co.uk, plus random others...
nslookup and dig ok
ping domain_name gives "Name or service not known"
ping ip ok
FF: Hmmm problem etc...

So this is my resolv.conf which is def linked to
/run/resolvconf/resolv.conf rather than the systemd stub-resolv.conf:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 192.168.2.1
nameserver 127.0.0.53
options edns0

I do have resolvconf installed (think I upgreded to Mint 19 from 18.3 so that explains it...)...
will remove and report back...

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