maas dhcp responses do not have domain-name or domain-search

[Scott Moser]

As found while debugging on bug 1116700, responses from the maas dhcp server do not have a 'domain-name' or 'domain-name-search' entries.

This has not been a glaring problem so far because fully qualified domain names are available.

It does seem, though that maas should at very least send the domain-name that corresponds to its domainname setting.

[Julian Edwards (julian-edwards)]

There's actually a school of thought that says MAAS should return the IP address and not the name at all. That would make this bug moot.

[James Page (james-page)]

Julian - not sure I agree 100% with your comment in #1.

Specifically this breaks code outside of Juju+MaaS which relies on the hostname being resolvable without a domain name suffix.

This is case with libvirt based live migration in OpenStack.

[Julian Edwards (julian-edwards)]

James - fair enough then. But it's trivial to add a search config to external resolv.conf, is that enough to help? Or are you concerned about the nodes themselves being unable to resolve hosts?

[Mark Shuttleworth (sabdfl)]

Julian, Jeroen, I think the preferred approach is to put the domain-search into the DHCP config:

  option domain-name cloud.mallards;
  option domain-name-servers 192.168.9.1;
  option domain-search "cloud.mallards";

Mark

[Kurt (burnbrighter)]

Julian - can we get this regressed to other branches too?

[Julian Edwards (julian-edwards)]

You have to file an SRU request and someone will backport it.