I'm also un-marking Incomplete as I think there's enough information
from the reporter to attempt to reproduce.
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
And Incomplete (or maybe Invalid) for netplan, since I agree with
Mathieu's assessment, at least based on what we know right now.
** Changed in: netplan.io (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm not sure that it's the same issue, but bug 1811554 fits into the
same category of "performance/reliability issue with named under edge
case" to me. I think this needs to go into the backlog of things that
need deep investigation.
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
Well, this would squarely be a bind9 issue. The use of 'netplan apply'
there just means that an IP might have changed, or the state of the
interface changed enough (bringing it down, then up again, readding
static addresses, etc) that bind couldn't make sense of it.
'netplan apply' is supposed to
I added a netplan.io bug task so that cyphermox sees this ug as well.
He will know best all the substeps that happen one "netplan apply" and if one
of them could be related. Furthermore he might have seen such reports but
against netplan.io instead of bind.
** Also affects: netplan.io (Ubuntu)
I apologize for the vague information, answers below:
- is bind on the same server where you ran netplan apply?
Yes, bind is running on the system where the netplan apply was done.
- when you say "long response times from the server", do you mean bind
(wherever it is running), or 127.0.0.53, whi
You should also check the output of systemd-resolve --status, as that
will tell you which dns servers the 127.0.0.53 resolver is using.
You also need to clarify this statement: "After the netplan apply completed
within 2 minutes we started seeing timeouts and long response times from the
server.
You are correct, right now /etc/resolv.conf has only the below entry:
nameserver 127.0.0.53
search companydomain.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811554
Title:
bind9 slow response
What does /etc/resolv.conf look like? Is it using bind9 as the
nameserver, or systemd-resolve (127.0.0.53)? You might not even be using
bind9 directly, but via systemd-resolve, so that changes how this should
be debugged.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You rece
