[Bug 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache

[Eric Desrochers]

You can find it here:
https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd?id=1401429&page=2

-----
Version: 237-3ubuntu10.23	2019-06-21 00:06:25 UTC
  systemd (237-3ubuntu10.23) bionic; urgency=medium

  * d/p/resolved-do-not-hit-CNAME-in-NODATA.patch:
    - fix stub resolver cache (LP: #1818527)

 -- Heitor Alves de Siqueira <email address hidden> Tue, 04 Jun 2019
15:54:24 -0300

Source diff to previous version
1818527	Stub resolver cache is corrupted
-----

The fix has been first introduced in "237-3ubuntu10.23" so
"237-3ubuntu10.38" definitely should have it still, yes.

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

Title:
  resolve: do not hit CNAME or DNAME entry in NODATA cache

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  The question: DNS A record lookups fail to resolve due to cached CNAME
  NODATA lookups ...

  https://askubuntu.com/questions/1063462/18-04-server-systemd-resolve-
  returns-cached-cname-nodata-for-a-lookup

  Upstream at Github: Systemd issue 998 - Cached cname NODATA returned
  for A lookup ...

  https://github.com/systemd/systemd/issues/9833

  
  Please patch ...

  https://github.com/systemd/systemd/commit/3740146a4cbd99883af79e375ee4836206dcea4e

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