Public bug reported: 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 ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe -- 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: Neutron ports dns_assignment does not match the designate DNS records for Neutron port Status in neutron: New 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
