Sorry. I meant Have, I’m on phone as middle of the night here.
I’m prepared to relax the check for dns.mode none networks. As in that case there can be no dns name conflict.
But for the other network you have 3 nics connected to the same network (all of which could potentially use dhcp using the same name, but in your case 2 out of the 3 are statically configured with additional subnets that lxd doesn’t know about).
I dont think we should explore the route of returning multiple ips (of the same protocol) for a single dns name as it would be confusing to use for reaching services on those names. As the services may be listening on a specific ip.
The proper way to set this up is to have 3 managed networks. Then you wouldn’t get name conflicts and you wouldn’t be running multiple subnets over the same bridge (which is rather unorthodox as you dont have layer 2 separation between subnets).
The other approach is to use the vlan settings on the bridged nic as we support running multiple vlans over the same bridge (with no dhcp or gateway).
We could then relax the dns name check to only those NICs in the default vlan that can use the networks dns.
See vlan filtering in LXD 4.2 has been released