Trent Lloyd (lathiat) wrote on 2018-10-11:
> Obvious fix to me would be to use the default space as the gateway, if it has one, otherwise fall > back to finding a space that has a gateway.
+1 for this, faced same issue where an application (designate-bind) has bindings to two MAAS subnets, both defined with default gateways and first LXD multiple default gateways in ip r l, second the active one went through dns-frontend space binding, instead of the default space binding.
Trent Lloyd (lathiat) wrote on 2018-10-11:
> Obvious fix to me would be to use the default space as the gateway, if it has one, otherwise fall > back to finding a space that has a gateway.
+1 for this, faced same issue where an application (designate-bind) has bindings to two MAAS subnets, both defined with default gateways and first LXD multiple default gateways in ip r l, second the active one went through dns-frontend space binding, instead of the default space binding.