osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Metadata service caching old nameservers?


Hi All,

We have a bit of a weird issue with resolv.conf for instances. We have 
changed our subnets in neutron to use googles nameservers which is fine. 
However it seems that when instances are launched they are still getting 
the old nameserver settings as well as the new ones. If I look at the 
metadata networking service it returns the old nameservers as well as 
the new ones below:

curl -i http://169.254.169.254/openstack/2017-02-22/network_data.json
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Content-Length: 753
Date: Thu, 29 Aug 2019 09:40:03 GMT

{"services": [{"type": "dns", "address": "178.18.121.70"}, {"type": 
"dns", "address": "178.18.121.78"}, {"type": "dns", "address": 
"8.8.8.8"}, {"type": "dns", "address": "8.8.4.4"}]

In our neutron dhcp-agent.ini file we have the correct dnsmasq 
nameservers set:

dnsmasq_dns_servers = 8.8.8.8, 8.8.4.4

Are there any database tables I can change or clear up to ensure the old 
nameservers no longer get set? I can't seem to find any reference in our 
config any more of the old nameservers, so I assume one of the services 
is still setting them but I can't figure out what is.

Any help will be much appreciated.

Many thanks,

-- 

Grant Morley
Cloud Lead, Civo Ltd
www.civo.com <https://www.civo.com/>| Signup for an account! 
<https://www.civo.com/signup>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190829/4df4728a/attachment.html>