Ask Your Question

DNS Resolution fails

asked 2017-06-20 17:09:26 -0500

Micha gravatar image


on my Mitaka installation on Ubuntu I use Neutron for networking.

I have some issues with DNS Resolution at the moment. I set my own domain name by setting


dns_domain = mydomain.

I also set


extension_drivers = port_security,dns

For test reasons.

This results in the following:

  1. Hostname -A still shows something along host-192-168-10-3.openstacklocal
  2. Hostname -f fails with hostname: Name or service not known
  3. curl shows correct_hostname.novalocal

I then set the following



Now I get:

  • the correct output when curling the metadata server
  • the correct output when showing the port (talking about dns_assignment and dns_name)

But still:

  • the wrong domain when asking for hostname -A - host-192-168-10-3.openstacklocal
  • a failing hostname -f

Further confusion ensures when taking a look at the dnsmasq config files:

/var/lib/neutron/dhcp/207cc6aa-ede3-465f-bee3-2e85d864fc18/addn_hosts    host-192-168-10-2.mydomain. host-192-168-10-2    host-192-168-10-3.openstacklocal host-192-168-10-3    host-192-168-10-1.mydomain. host-192-168-10-1

but those are now missing from the leases file


1498080444 fa:16:3e:e9:3c:43 host-192-168-10-3 *
1498080317 fa:16:3e:bc:6f:16 host-192-168-10-2 *

I have a hard time understanding what is happening here and how to fix. All I want is a working hostname -f (which will result in working sudo without touching any files on the instance) and my custom domain.

Also I read this spec: (

Does anybody know if this was already implemented in newton/ocata?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-07-05 11:28:36 -0500

Micha gravatar image

Just fyi: In Mitaka the domain name for the metadata is always set via nova.conf. Ping an Instance via Hostname is not possible.

After upgrading to Newton, this now works :)

edit flag offensive delete link more


Would you happen to have any details to share on this issue, bug reports or whatnot? I'm facing similar issues on a Mitaka installation that can't easily be upgraded.

timss gravatar imagetimss ( 2017-07-13 05:57:33 -0500 )edit

Unfortunatly I never digged deeper into that issue. I assume that the l3 agent is missing the functionality to load the user data from the config, but I'm not sure since I'm quite new to openstack.

Micha gravatar imageMicha ( 2017-08-10 11:01:23 -0500 )edit

All right, thanks for the heads up anyway! :)

timss gravatar imagetimss ( 2017-08-10 13:17:31 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-06-20 17:09:26 -0500

Seen: 960 times

Last updated: Jul 05 '17