[Openstack-operators] [openstack-dev] [Neutron] Allowing DNS suffix to be set per subnet (at least per tenant)

Maish Saidel-Keesing maishsk at maishsk.com
Thu Sep 3 19:56:39 UTC 2015

On 09/03/15 20:37, Steve Wormley wrote:
> As far as I am aware it is not presently built-in to Openstack. You'll 
> need to add a dnsmasq_config_file option to your dhcp agent 
> configurations and then populate the file with:
> domain=DOMAIN_NAME,CIDR for each network
> i.e.
> domain=example.com <http://example.com>, 
> <>
> ...
> -Steve
Thanks Steve,

I am aware of that 'hack' which has a substantial number of downsides.

The biggest one being that it per subnet - and I afraid to find out what 
would happen if more than one tenant configures the same subnet - this 
could cause all sorts of problems.

And all of this has to be done with appropriate shell permissions to the 
neutron node.

In other words, it could work, but only for a very certain use case.

> On Thu, Sep 3, 2015 at 1:04 AM, Maish Saidel-Keesing 
> <maishsk at maishsk.com <mailto:maishsk at maishsk.com>> wrote:
>     Hello all (cross-posting to openstack-operators as well)
>     Today the setting of the dns suffix that is provided to the
>     instance is passed through dhcp_agent.
>     There is the option of setting different DNS servers per subnet
>     (and and therefore tenant) but the domain suffix is something that
>     stays the same throughout the whole system is the domain suffix.
>     I see that this is not a current neutron feature.
>     Is this on the roadmap? Are there ways to achieve this today? If
>     so I would be very interested in hearing how.
>     Thanks
>     -- 
>     Best Regards,
>     Maish Saidel-Keesing

Best Regards,
Maish Saidel-Keesing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150903/ee032cac/attachment.html>

More information about the OpenStack-operators mailing list