** Description changed: - - When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the initial dhcp is always the hostname 'ubuntu', and this is recorded in the dnsmasq's dhcp leases file. + When using the normal lxd-bridge, using a dnsmasq instance for dhcp, the + initial dhcp is always the hostname 'ubuntu', and this is recorded in + the dnsmasq's dhcp leases file. Presumably the dhcp is done before the container's hostname is set. A restart or dhcp renew seems to put the correct container name in the leases file. - This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable with a restart or renew. - + This is a problem when using the dnsmasq for local dns resolving for + *.lxd, which is the standard way of doing host dns for containers, as + new containers are not dns addressable without a restart or renew. Is there anyway get the correct hostname in the initial dhcp? Or maybe renew after setting the hostname?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600766 Title: initial dhcp has default hostname of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
