Re: [Rdo-list] the hostname returned by metadata service ?

Hi Xin, The hostname inside of the guest is typically set via the metadata service, which is native to Nova, and not the Neutron service. Inside of your Nova configuration file you’ll see this configuration option- [root@stack-node1 ~(keystone_demo)]# grep dhcp_domain /etc/nova/nova.conf #dhcp_domain=novalocal Which is why when you launch an instance, the cloud-init (or similar) service configures the local hostname based on this, and not what the DHCP service is giving out. You can test this inside of your instance: $ curl http://169.254.169.254/latest/meta-data/local-hostname test1.novalocal However, the DHCP agent will report a different hostname associated to that host; you can confirm this inside of the namespace (or as you have done it inside of your instance): [root@stack-node1 ~(keystone_demo)]# ip netns exec qdhcp-0dc9eedc-1077-41cb-a615-f63fb2538aaf host 172.16.0.12 172.16.0.1 Using domain server: Name: 172.16.0.1 Address: 172.16.0.1#53 Aliases: 12.0.16.172.in-addr.arpa domain name pointer host-172-16-0-12.openstacklocal. So, you’ve got two choices here- 1) You update the nova configuration to the DHCP domain that you require, and leave the instances to set their hostname via metadata 2) You re-configure your cloud-init configuration to NOT use the metadata service for the hostname and use normal DHCP setting Cheers Rhys