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

2020-06-01 Thread Dan Streetman
> Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. the 'NXDOMAIN' messages are not related to this bug, a bit more detail is in this comment

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

2020-05-30 Thread Jerry Quinn
I have the same problem in 237-3ubuntu10.41 amd64 May 30 12:55:59 cerberus systemd-resolved[1595]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. -- You received this bug notification because you are a

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

2020-04-17 Thread Peter Goodall
I have the same problem with 237-3ubuntu10.39 amd64 ``` systemd-resolved[2198]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] % lsb_release -a No LSB modules are available.

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

2020-02-05 Thread Eric Desrochers
You can find it here: https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd?id=1401429=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

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

2020-02-05 Thread xichen
hi, Eric: Could you please confirm that this bug had been fixed on ubuntu bionic with version 237-3ubuntu10.38? I am confusing about your comment as I found nothing when go through the update changes https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd. -- You received

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

2020-01-21 Thread Eric Desrochers
Bionic has been applied via LP: #1818527 introduced in version: systemd (237-3ubuntu10.23) bionic; urgency=medium * d/p/resolved-do-not-hit-CNAME-in-NODATA.patch: - fix stub resolver cache (LP: #1818527) ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Fix Released **

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

2020-01-21 Thread Eric Desrochers
** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Tags added: st ** Tags removed: st ** Tags added: sts -- You received this bug notification because you are a member of

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

2020-01-21 Thread Eric Desrochers
Seems like Disco and late already have the requested fix. $ git describe --contains 3740146a4cbd99883af79e375ee4836206dcea4e v240 $ rmadison systemd systemd | 204-5ubuntu20| trusty | source systemd | 204-5ubuntu20.31 | trusty-security | source, amd64, arm64, armhf, i386, powerpc,

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

2020-01-21 Thread Jorge Niedbalski
** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu

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

2019-04-08 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1818527 *** https://bugs.launchpad.net/bugs/1818527 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of

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

2019-04-08 Thread Chiang Fong Lee
*** This bug is a duplicate of bug 1818527 *** https://bugs.launchpad.net/bugs/1818527 ** This bug has been marked a duplicate of bug 1818527 Stub resolver cache is corrupted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

2019-03-30 Thread Matt Frisch
I stopped using resolve because of this bug so unfortunately, I can't say whether or not that error appeared in the log at the same time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822416 Title:

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

2019-03-30 Thread Frans van Berckel
Extra question: is Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP, as pointed related? https://www.linode.com/community/questions/17384/error-server-returned-