Right now, we set a single domain name per deployment, stated in the neutron configuration file. However, there are use cases where it is useful to provide more granularity to DNS, like at a network or port level where the dns_domain attribute exists. The goal of this RFE is to support DNS domains at a network level just in the ML2/OVN driver by adding a new extension. This is a feature that has been requested by customers. There are several use cases for this: * In a multitenant environment, different users working on different projects use common hostnames for their VMs, which leads to a FQDN conflict. Users don’t have to know the hostnames other VMs have, so they could generate an unexpected FQDN clash. * In a multitenant environment, users working in an application with different stages might want to re-use hostnames and make a distinction on the domain. Example: app001.uat.example.com (for UAT) vs app001.prd.example.com (for Production) both have the same hostname. Additional info upstream: https://review.opendev.org/c/openstack/neutron-specs/+/832658 https://bugs.launchpad.net/neutron/+bug/1960850