Comment 4 for bug 1811554

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, which in turn may query the bind server you are talking about?

After the netplan apply command was run some queries made to the nameserver start timing out. When failing dig/nslookup would say that no name server could not be reached. Some queries would receive a response after 5-10 seconds with a 0-1ms query time. Finally some queries returned responses as expected.

- 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.

The queries were run from a workstation to the nameserver. Both "dig @<server> <name>" and "nslookup <name> <server>" were attempted.

I did not attempt to use the 127.0.0.53 resolver on the nameserver during the issue as I did not know bind was utilizing it. If the opportunity presents itself I will test the resolver as well.

-----

Results from systemd-resolve --status

Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 3 (ens192) - Private IP, Management Network
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 2 (ens160) - Public IP
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: y.y.y.y (Primary Caching Server)
                      x.x.x.x (Servers own public IP)