[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Dimitri John Ledkov]

127.0.0.53 stub resolver was only introduced in v231, thus there is
nothing to fix in xenial.

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-9ubuntu4

---
systemd (231-9ubuntu4) yakkety; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target.  LP: #1673860.
  * debian/patches/resolved-follow-CNAMES-for-DNS-stub-replies.patch:
Cherry-pick upstream fix for resolved failing to follow CNAMES for DNS
stub replies. LP: #1647031.
  * debian/patches/logind-update-empty-and-infinity-handling-for-User-T.patch:
Cherry-pick upstream fix to handle empty and "infinity" values for
[User]TasksMax.  Closes LP: #1651518.

 -- Steve Langasek   Mon, 20 Mar 2017
22:14:14 -0700

** Changed in: systemd (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

Verified by way of a slightly modified test case:
 - boot a yakkety cloud image
 - verify 127.0.0.53 in /etc/resolv.conf
 - sudo sed -i -e's/resolve \[[^]]*\] //' /etc/nsswitch.conf
 - ping www.freedesktop.org -> FAIL
 - install systemd from -proposed
 - ping www.freedesktop.org -> SUCCESS


** Tags removed: verification-needed
** Tags added: verification-done

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Andreas Lindhé]

** Bug watch added: github.com/nextcloud/nextcloud-snap/issues #178
   https://github.com/nextcloud/nextcloud-snap/issues/178

** Also affects: nextcloud-snap via
   https://github.com/nextcloud/nextcloud-snap/issues/178
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

I was reminded that libnss-resolve is in 'standard' now, which means
it's also installed by default on server and any bugs that affect only
the stub DNS resolver without affecting the dbus service - such as this
one - do not impact DNS resolution by default on server in 16.10.

(I was wondering why no one had reported it before now.)

So, I'm downgrading this from critical to high since it only hits users
of 16.10 server in a few corner cases (i.e. containers, chroots without
libnss-resolve installed).  It should still be SRUed.

** Changed in: systemd (Ubuntu Yakkety)
   Importance: Critical => High

** Changed in: network-manager (Ubuntu Yakkety)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?

Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track that problem separately?

** Also affects: network-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Yakkety)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: systemd (Ubuntu Yakkety)
Milestone: None => yakkety-updates

** Changed in: systemd (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 232-17ubuntu1

---
systemd (232-17ubuntu1) zesty; urgency=medium

  * debian/patches/0001-resolved-follow-CNAMES-for-DNS-stub-
replies.patch: cherry-pick upstream fix for following CNAMEs in DNS
stub replies.  Closes LP: #1647031.

 -- Steve Langasek   Sun, 12 Feb 2017
22:54:55 -0800

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.4.2-3ubuntu2

---
network-manager (1.4.2-3ubuntu2) zesty; urgency=medium

  * Revert 98974a88 and 47c16e59 (network-manager switching from dnsmasq
to resolved) because of bugs in resolved's resolution of CNAME
records.  (LP: #1647031)

 -- Barry Warsaw   Thu, 05 Jan 2017 15:26:55 -0500

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Barry Warsaw]

As per pitti's email in #12, added network-manager bugtask and
subscribed pitti.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Barry Warsaw (barry)

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-17.04

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Steve Langasek]

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: glibc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs