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." - is bind on the same server where you ran netplan apply? - when you say "long response times from the server", do you mean bind (wherever it is running), or 127.0.0.53, which in turn may query the bind server you are talking about? - how did you query the nameserver, was it using a directed tool like dig querying the server directly (dig @<server> <name>), or using the 127.0.0.53 resolver with something generic like "ping <name>", or "host <name>"? There are many pieces involved in name resolution. We need better reproduction steps in order to evaluate this issue and determine if it's a bug or not. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1811554 Title: bind9 slow response after netplan apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1811554/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
