Designate PTR record creation results in in-addr.arpa. zone owned by invalid project ID

[Drew Freiberger]

When Neutron is creating PTR records during Floating IP attachment on Stein, we have witnessed the resultant new X.Y.Z.in-addr.arpa. zone is owned by project ID 00000000-0000-0000-0000-000000000000.

This creates issues for record updates for future FIP attachments from Neutron resulting in API errors.

Workaround is to change the project-ID to the services project_id in the services_domain.

[Dr. Jens Harbott (j-harbott)]

You shouldn't be using Designate's PTR feature at the same time as Neutron's dns_integration, those two are not meant to co-exist.

If you want to use designate, set the [service:central]managed_resource_tenant_id variable to the project that you want designate to use for managed resources, the default is 00000000-0000-0000-0000-000000000000, so designate is working as designed here. But then disable dns_integration from trying to handle PTR zones.

Or have dns_integration handle PTR records, but then tell Designate not to deal with them.