Comment 3 for bug 1784879

I think that these are valid use cases, I have another similar one: public IPv6 networks in project networks according to https://cloudbau.github.io/openstack/neutron/networking/ipv6/2017/09/11/neutron-pike-ipv6.html , where users get public IPv6 addresses for their instances and want to have DNS records for these.

My use case would even go a step further in that I would want to select per subnet whether DNS entries are published and not only per network. One idea I had was to use the address scope property of the subnet for making that decision, but having an explicit flag that can be specified per network, subnet or even per port would probably be the most flexible solution.