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
the Neutron port dns_assignment dont match the designate DNS records assigned to the Neutron port
as explained in the link below /docs.openstack .org/neutron/ pike/admin/ config- dns-int. html
https:/
when a user creates a neutron port using the command below 6047-45ac- bf4f-a825e56fd2 b3 \
neutron port-create 37aaff3a-
--dns-name my-vm --dns_domain port-domain.org.
The actual output for dns_assignment is: example. org."} example. org."}
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn": "my-vm.
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn": "my-vm.
and the Designate DNS records is 7e3c-4fb1- 9261-0481318bb7 b5 | A | my-vm.port- domain. org. | 203.0.113.9 9969-47aa- 82e1-e057540218 52 | AAAA | my-vm.port- domain. org. | 2001:db8:10::9
67a8e83d-
5a4f671c-
while the expected output for dns-assignment: port-domain. org."} port-domain. org."}
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn": "my-vm.
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn": "my-vm.
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