Strange IPv6 DNS issue after upgrade from 3.3 to 3.4

I upgraded to 3.4/edge to pick up the fix for Bug #2053033 “Creating MAAS Virsh VM does not work (libvirt: err...” : Bugs : MAAS, but there seems to be some kind of DNS regression wrt IPv6 addresses in 3.4. I filed Bug #2054915 “Failed configuring DHCP on rack controller - too m...” : Bugs : MAAS and I’m continuing to debug, but I was wondering if anyone here had seen a similar issue after upgrade to 3.4.

I see they were committed, if you still see some issues please report them! Thank you for spending time to report these issues :+1: