Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.
** Changed in: resolvconf (Ubuntu Cosmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: resolvconf (Ubuntu Disco)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
Before trying to handle this as a BUG (and I know the behavior points to
a bug) please have a look at
https://github.com/Azure/WALinuxAgent/issues/1673
** Bug watch added: github.com/Azure/WALinuxAgent/issues #1673
https://github.com/Azure/WALinuxAgent/issues/1673
--
You received this bug not
** Tags added: id-5cde5f8331588344774efccb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
To manage notifications about th
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Bionic)
Status: New => Triaged
** Changed in: resolvconf (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: resolvconf (Ubuntu Disco)
Status: New => Triaged
The conclusion of a very long IRC discussion about how to fix this is
that we should change the resolvconf package in the presence of resolved
to emit only 127.0.0.53 into /etc/resolv.conf, and redirect all other
servers to resolved.
--
You received this bug notification because you are a member
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple
The fix (workaround) for this bug in bionic and cosmic was to add
'options edns0' to the /etc/resolv.conf file via the systemd stub-
resolv.conf file.
However, when the resolvconf package is installed, due to bug 1817903,
the 'options edns0' is stripped out of the /etc/resolv.conf file.
This mean
** Changed in: systemd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
To manage notific
It seems this breaks dns lookups on some system, see #1817903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
To manage not
This bug was fixed in the package systemd - 239-7ubuntu10.7
---
systemd (239-7ubuntu10.7) cosmic; urgency=medium
* d/p/resolve-enable-EDNS0-towards-the-127.0.0.53-stub-res.patch
getaddrinfo() failures when fallback to dns tcp queries, so enable
edns0 in resolv.conf (LP: #181
This bug was fixed in the package systemd - 237-3ubuntu10.12
---
systemd (237-3ubuntu10.12) bionic; urgency=medium
* d/p/resolve-enable-EDNS0-towards-the-127.0.0.53-stub-res.patch
getaddrinfo() failures when fallback to dns tcp queries, so enable
edns0 in resolv.conf (LP: #1
All remaining bionic and cosmic autopkgtest regression failures should be
ignored.
bionic regressions:
systemd on all archs have failed for months, ignore
linux-gcp-edge fails due to timeout in test while rebuilding; ignore
linux has flaky tests - intermittently fails for a long time, ignore
This bug was fixed in the package systemd - 240-5ubuntu3
---
systemd (240-5ubuntu3) disco; urgency=medium
* debian/tests: blacklist upstream test-24-unit-tests on ppc64le.
Fails, not a regression as it's a new test case, which was never before
executed on ppc64le.
File:
hddemux failure should be ignored; its autopkgtests are fixed in
-proposed with bug 1814062
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple
bionic regressions:
systemd on all archs have failed for months. tests should be ignored.
snapd on all archs have failed intermittently for very long time. tests
are flaky and should be ignored.
remaining tests being retried:
linux-gcp-edge (system problem - oom while testing)
linux (flaky t
autopkgtest regression failure analysis/justifications for bionic:
systemd/s390x - failing since last november.
gvfs/s390x - failing since 2017.
snapd/s390x - flaky test that fails more than 1/2 the time since forever.
snapd/ppc64el - same as s390x
for cosmic:
gvfs/s390x - almost always faile
Bionic verified
ii systemd 237-3ubuntu10.12 amd64 system and service manager
$ ping testing.irongiantdesign.com
PING testing.irongiantdesign.com (253.0.0.6) 56(84) bytes of data.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bio
Cosmic Verified
ii systemd 239-7ubuntu10.7 amd64
system and service manager
ping testing.irongiantdesign.com
PING testing.irongiantdesign.com (253.0.0.15) 56(84) bytes of data.
** Tags removed: verification-needed-cosmic
** Tags added: verifica
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Dan, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu Disco)
Assignee: Dan Streetman (ddstreet) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Trusty)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Xenial)
Importance: High => Undecided
** Changed in: systemd (Ubuntu Trusty)
Importance: High => Undecide
** Description changed:
[Impact]
The systemd local 'stub' resolver handles all local DNS queries (by
default configuration used in Ubuntu), and essentially proxies all
requests to its configured upstream DNS resolvers.
Most local DNS resolution by applications uses glibc's getaddri
** Patch removed: "lp1811471-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811471/+attachment/5233684/+files/lp1811471-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "lp1811471-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811471/+attachment/5233684/+files/lp1811471-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
To manage notifications about this bug go to:
https://bugs.launchpad.net/sys
> Also is this then just not a simple cherrypick of:
>
> https://github.com/systemd/systemd/commit/93158c77bc69fde7cf5cff733617631c1e566fe8
that's one way to work around it, although glibc is not necessarily the
only thing that might do pipelined TCP dns lookups to the local stub
resolver (though
Also is this then just not a simple cherrypick of:
https://github.com/systemd/systemd/commit/93158c77bc69fde7cf5cff733617631c1e566fe8
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
I am happy to add "options edns0" in the generated file by resolved.
But we also need to file this case upstream, and start implementing
pipelined requests handling in resolved too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Adding "options edns0" to /etc/resolv.conf ended up resolving bug
1805027 for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns qu
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TCP dns queries
To manage notification
** Bug watch added: github.com/systemd/systemd/issues #11332
https://github.com/systemd/systemd/issues/11332
** Also affects: systemd via
https://github.com/systemd/systemd/issues/11332
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
33 matches
Mail list logo
