Comment 5 for bug 1650678

I am not sure the bug just suggests that dns_domain is used for tagging purpose.

In a provider network deployment scenarios, all VMs belong to a single network. There may be a case where some set of VMs belong to service A with foo.example.net and other set of VMs belong to service B with bar.example.net. In such case, dns_domain per port might be needed. I think it is a valid use case.

We already allows users to assign both dns_domain and dns_name for a specific floating IP, so I am not sure there is a reason we do not allow dns_domain per port.

Note that if the self-service network model is used, you can define neutron network per service (i.e. business unit in the bug description) and assign dns-domain for individual neutron network.