Comment 2 for bug 1698010

Thanks for the detailed report. It looks like we're populating the config drive with the value of nova-network's 'dhcp_domain' option, rather than using neutron's 'dns_domain' as one would expect. I've updated the title of the bug report accordingly.

I'm going to take a look at this, but in the interim it's the config drive and/or metadata service that we should be looking at. I would guess this chunk of code [1] is at least somewhat related.

[1] https://github.com/openstack/nova/blob/0b9bacb/nova/api/metadata/base.py#L546-L549