Comment 5 for bug 2012391

Yes, it was created with Terraform however, creating a server through the CLI or Horizon is even worst.
The fqdn set at the port level only account for the cluster global domain ("test.ops.testcloud.fr") and not the tenant based fqdn I expect ("test.tenant.ops.testcloud.fr").
Because of this, reverse DNS is not working and things like "sudo" or "hostname -f" are very slow because those commands wait until the reverse times out.

"hostname -A" works as expected, it provides the FQDN with no delay so I don't know exactly where the difference is.
However, in the case of Terraform, I can "forge" the FQDN at the port level and thus, I retrieve the good FQDN inside the instance through "hostname -A" but this is a trick and it doesn't work if I spawn an instance through CLI/Horizon though.

It looks like it just d'ont care about Designate and the zone assigned to the tenant and only care about the global domain which is cluster wide which is definitely not what I want.