...you can create a list of one or more resolvers for dnsmasq to use for tenant networks. (Designate uses unbound in downstream RHOSP.) The problem is, that configuration doesn't have a concept of the AZ or edge site. Therefore, setting one list of resolvers for all of neutron might be a problem for some OSP sites that also use edge deployments.
From the designate-edge point of view:
Problem space:
We want to use the upstream neutron doc to understand how to configure dnsmasq to hit a local resolver at an edge site.
In this neutron doc topic:
https:/ /docs.openstack .org/neutron/ yoga/admin/ config- dns-res. html#case- 2a-queries- are-forwarded- to-an-explicitl y-configured- set-of- dns-resolvers
...you can create a list of one or more resolvers for dnsmasq to use for tenant networks. (Designate uses unbound in downstream RHOSP.) The problem is, that configuration doesn't have a concept of the AZ or edge site. Therefore, setting one list of resolvers for all of neutron might be a problem for some OSP sites that also use edge deployments.