Comment 10 for bug 475354
Revision history for this message
| Daniel Nurmi (nurmi) wrote Re: Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Some more context: if the eucalyptus DNS feature is disabled (as it is in the UEC, by default), then we cannot guarantee that the IP addresses that are specified by the administrator resolve to an actual hostname (as, often, users are choosing private/unroutable IP addresses for VMs). Inventing a hostname here will break other services that rely on this information as being string that can be passed other network services. This is the reason why, when the Eucalyptus DNS service is disabled, we put an IP address in this field.
To us, the first priority of this field is to return 'a string that can be used as a network endpoint' rather than 'a string that the hostname command handles properly'.
If a Eucalyptus user requires a legitimate hostname here, then it is best to enable the Eucalyptus DNS service as detailed here:
http://