This would explain a LOT of our deployment failures, especially when I run multiple deployments concurrently.
I checked our own server and: $ grep "starting BIND" named.log*|awk '{print $1}'|sed "s/.*://"|sort|uniq -c 853 19-Oct-2023 1127 20-Oct-2023 1386 21-Oct-2023 1335 22-Oct-2023 827 23-Oct-2023 830 24-Oct-2023 619 25-Oct-2023 22 26-Oct-2023 3 27-Oct-2023 6 28-Oct-2023
We are currently on this version of the MAAS snap: maas 3.4.0~rc1-14302-g.bb0dc28c1 30266 3.4/candidate canonical✓ -
But have been seeing this same behaviour (lost of DNS resolution under load) since at least 3.3.x, perhaps a touch older.
I'm adding a sosreport from our own server as well.
This would explain a LOT of our deployment failures, especially when I run multiple deployments concurrently.
I checked our own server and:
$ grep "starting BIND" named.log*|awk '{print $1}'|sed "s/.*://"|sort|uniq -c
853 19-Oct-2023
1127 20-Oct-2023
1386 21-Oct-2023
1335 22-Oct-2023
827 23-Oct-2023
830 24-Oct-2023
619 25-Oct-2023
22 26-Oct-2023
3 27-Oct-2023
6 28-Oct-2023
We are currently on this version of the MAAS snap: 14302-g. bb0dc28c1 30266 3.4/candidate canonical✓ -
maas 3.4.0~rc1-
But have been seeing this same behaviour (lost of DNS resolution under load) since at least 3.3.x, perhaps a touch older.
I'm adding a sosreport from our own server as well.