Whereas we have discussed this in the past and we agreed to comply with the spec for internal dns resolution (https://specs.openstack.org/openstack/neutron-specs/specs/liberty/internal-dns-resolution.html) as recorded here http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-05-29-14.00.log.html#l-42, I think more use cases have surfaced recently that warrant a reevaluation of this decision and of the original spec. Just last week, I was talking to hjensas in the Neutron channel, and he was describing a very similar need (if not the same): "in our case we have multiple ports for each instance, and instead of $server-name.$netname.example.com. they all get £server-name.example.com. now. Which is confusing. Since $netname.example.com. is in the dns_domain of the network ..." (http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2020-04-17.log.html#t2020-04-17T14:54:11).
I think it is time to explore a way to satisfy these new use cases while providing backwards compatibility with the original spec mentioned above.
Whereas we have discussed this in the past and we agreed to comply with the spec for internal dns resolution (https:/ /specs. openstack. org/openstack/ neutron- specs/specs/ liberty/ internal- dns-resolution. html) as recorded here http:// eavesdrop. openstack. org/meetings/ neutron_ l3/2019/ neutron_ l3.2019- 05-29-14. 00.log. html#l- 42, I think more use cases have surfaced recently that warrant a reevaluation of this decision and of the original spec. Just last week, I was talking to hjensas in the Neutron channel, and he was describing a very similar need (if not the same): "in our case we have multiple ports for each instance, and instead of $server- name.$netname. example. com. they all get £server- name.example. com. now. Which is confusing. Since $netname. example. com. is in the dns_domain of the network ..." (http:// eavesdrop. openstack. org/irclogs/ %23openstack- neutron/ %23openstack- neutron. 2020-04- 17.log. html#t2020- 04-17T14: 54:11).
I think it is time to explore a way to satisfy these new use cases while providing backwards compatibility with the original spec mentioned above.