Comment 4 for bug 1088584

I have some notes for future consideration about auto creating internal domain names.

Probably all user expects, they can choose user friendly "name"s regardless "name"s used by any other tenant in all configuration.

Some application may expect the FQDN has at least 3 part.
 <hostname>.<domain>.<TLD>.

Someone might want to use a single wildcard certificate even for the "internal" domain names.

AFAIK in several configuration, a tenant can have multiple network, and someone might wants the FQDN contains the network/subnet names too.

Some user might want even more customization...

Option:
Use the VMs UUID in the auto-generated FQDN and let the users to pick another names...
Auto-generated FQDN should be based on the network/subnet topology.
If the VM has multiple interface, it might need at least one entry for all interface.