[openstack-dev] [neutron] dns-nameservers order not honored
ihrachys at redhat.com
Wed Jun 24 08:40:04 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 06/23/2015 08:48 PM, Paul Ward wrote:
> I haven't dug into the code yet, but from testing via CLI and REST
> API, it appears neutron does not honor the order in which users
> specify their dns-nameservers. For example, no matter what order I
> specify 10.0.0.1 and 10.0.0.2 for dns-nameservers, they are always
> ordered with the numerically lowest IP first when doing a
> subnet-show (ie, 10.0.0.1 will be first, even if I specified
> 10.0.0.2 first). As stated above, CLI and REST API behave the
Strictly speaking, the order of nameservers in API has nothing to do
with what is passed to dnsmasq.
> I believe this is a problem because these are passed to activation
> on a deployed VM in the order neutron lists them in the subnet. A
> user may have a reason they want the numerically higher DNS IP
> listed first, say if they are trying to load balance their DNS
> servers. By always ordering them numerically, we give them no way
> to do this.
You still can achieve nameserver rotation on your instances with
'rotate' option in your /etc/resolv.conf.
> So my question is... is this by design or an oversight? If it's
> an oversight, I'll dig into the code and propose a patch.
I think patches are more than welcome.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the OpenStack-dev