This is fixed in focal.
** Changed in: bind9 (Ubuntu)
Status: In Progress => 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/1856367
Title:
systemd-resolvd breaks dig + trace
To
This is fixed in focal.
** Changed in: bind9 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856367
Title:
systemd-resolvd breaks dig +
I just uploaded new bind9 to focal, it's still building, but I didn't
mention this bug in d/changelog. I'll close it manually once it's
published.
** Changed in: bind9 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I just uploaded new bind9 to focal, it's still building, but I didn't
mention this bug in d/changelog. I'll close it manually once it's
published.
** Changed in: bind9 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server,
Confirmed fixed in the new version I'm preparing, I'll include a mention
of this bug in its d/changelog.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856367
Title:
systemd-resolvd
Confirmed fixed in the new version I'm preparing, I'll include a mention
of this bug in its d/changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856367
Title:
systemd-resolvd breaks dig +
> @Andreas - do you know the plans of 9.15 in regard to Ubuntu 20.04 will
> we get and merge this or should we consider backporting this fix individually?
9.15 is a devel release (odd), so not a good series to track for 20.04.
9.16 is their next extended support version, but I don't think it will
> @Andreas - do you know the plans of 9.15 in regard to Ubuntu 20.04 will
> we get and merge this or should we consider backporting this fix individually?
9.15 is a devel release (odd), so not a good series to track for 20.04.
9.16 is their next extended support version, but I don't think it will
Please note the different packages: systemd-resolvd breaks this
functionality "by design" and bind9/dig officially includes a patch to
work around this issue. The patch is officially accepted and merged in
bind9 repository and as @paelzer noted released as v9_15_2. So no delta
must be maintained
Thanks for flagging the upstream comment about the change. If this is
indeed 'by design' then that suggests this patch would need considered
to carry as part of the delta maintained for ubuntu's bind9 package - or
preferably in Debian.
One thing you could do to help move this forward would be to
** Also affects: bind
Importance: Undecided
Status: New
** No longer affects: bind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856367
Title:
systemd-resolvd breaks dig + trace
To
I know that dig +trace worked before systemd-resolvd was used.
Interpreting the following comment that this behavior is "by design", I
guess it was broken all the time:
https://github.com/systemd/systemd/issues/5897#issuecomment-300238951
** Bug watch added: github.com/systemd/systemd/issues
I was just checking if this might be backported already in some way
The fix changes:
case 'r':
switch (cmd[2]) {
case 'a': /* trace */
FULLCHECK("trace");
lookup->trace
Hi and thank you for your report.
This is applied upstream in v9_15_2
We are still at the latest point release of the 9.11 series.
I've seen 9.15.5-1 in the new queue already.
@Andreas - do you know the plans of 9.15 in regard to Ubuntu 20.04 will
we get and merge this or should we consider
14 matches
Mail list logo
