Public bug reported:

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

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to