Open Stack

>Is there an actual DNS service that will correctly return the IP address associated with these names or is it just a local host naming convention?
>
>- Mark

Hi Mark,

If you have the Neutron DNS extension enabled via extension_drivers = dns in ml2_conf.ini. The DHCP agent's Dnsmasq will act as a DNS server and should resolve the domain. You could then add the subnets DHCP address as the subnets DNS server. I believe DNS forwarders can also be set.

Regards,
Oisin


Oisin O'Malley
Systems Engineer
Iocane Pty Ltd
763 South Road
Black Forest SA 5035

Office:+61 (8) 8413 1010
Fax:+61 (8) 8231 2050
Email:oisin.omalley at iocane.com.au
Web:www.iocane.com.au

Better for business

>On Thu, Mar 30, 2017 at 2:49 PM Brian Haley <haleyb.dev at gmail.com> wrote:
>On 03/28/2017 08:39 PM, Oisin O'Malley wrote:
>>
>> There was 2 separate issues to resolve;
>>
>> Firstly Nova was appending the default domain name .novalocal to the hostname it presents via the meta-data service. This can be resolved by setting dhcp_domain to an empty string in nova.conf on the Control node. For instance 'dhcp_domain='. An instances name can now be set to a FQDN which will then be passed cloud-init via the metadata server.
>>
>> Secondly, The Neutron DHCP service sets the default DNS suffix for a NIC to openstacklocal . This causes delays in DNS lookups on external DNS servers, as the wrong domain is used by default. Similarly to the above, this can be resolve by setting 'dhcp_domain=' in the Neutron DHCP config file dhcp_agent.ini. Once this is set and the DHCP service restarted, the "--domain=<DOMAIN>" parameter no longer gets set

>Just an FYI that 'dhcp_domain' had been marked for deprecation and was
>finally removed in Ocata.  The new value is 'dns_domain', which lives in
>neutron.conf - the dhcp agent was changed to pick-up the new value.

>-Brian