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.
** Changed in: neutron
Status: Won't Fix => Triaged
** Changed in: neutron
Importance: Undecided => Wishlist
** Summary changed:
- Neutron ports dns_assignment does not match the designate DNS records for
Neutron port
+ [RFE] Neutron ports dns_assignment does not match the designate DNS records
for Neutron port
** Tags removed: rfe
** Tags added: rfe-triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1873091
Title:
[RFE] Neutron ports dns_assignment does not match the designate DNS
records for Neutron port
Status in neutron:
Triaged
Bug description:
the Neutron port dns_assignment dont match the designate DNS records
assigned to the Neutron port
as explained in the link below
https://docs.openstack.org/neutron/pike/admin/config-dns-int.html
when a user creates a neutron port using the command below
neutron port-create 37aaff3a-6047-45ac-bf4f-a825e56fd2b3 \
--dns-name my-vm --dns_domain port-domain.org.
The actual output for dns_assignment is:
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn":
"my-vm.example.org."}
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn":
"my-vm.example.org."}
and the Designate DNS records is
67a8e83d-7e3c-4fb1-9261-0481318bb7b5 | A | my-vm.port-domain.org. |
203.0.113.9
5a4f671c-9969-47aa-82e1-e05754021852 | AAAA | my-vm.port-domain.org. |
2001:db8:10::9
while the expected output for dns-assignment:
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn":
"my-vm.port-domain.org."}
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn":
"my-vm.port-domain.org."}
most likely right now the dns_domain is taken from the Neutron network
dns_domain or from neutron dns_domain configuration
A good approach would be to always make the dns_assignment for Neutron port
synced with the Designate DNS records if Designate is used
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1873091/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
