Fuel for OpenStack

What is the preferred way of setting up DNS when Fuel master doesn't have access to upstream DNS server?

Asked by Sam Stoelinga

Currently my openstack nodes can't access the DNS servers I specified in the fuel settings, because Fuel configures the openstack nodes to only uses the fuel master node as DNS server. From my understanding the fuel master node should be totally isolated and shouldn't have internet access.

Instead it would be nicer to have the specified DNS servers via the Fuel settings as 2nd and 3rd server on every openstack node's resolv.conf. The 1st DNS server being the fuel master node. This way even if the fuel master node can't access the upstream DNS servers, then still the openstack nodes would be able to access the upstream DNS servers. This way everything still works as expected because internal hostnames are still being resolved through our fuel master DNS server.

Is my above understanding correct and is it a proper way to handle this problem?
Any help greatly appreciated , thanks :)

Question information

Language:
English Edit question
Status:
Answered
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Evgeny Kozhemyakin (ekozhemyakin) said : 		#1

 You can distribute your preferred DNS configuration via dhcp from fuel master.
For this you have to edit /etc/cobbler/dnsmasq.template and then run "cobbler sync" command.
Search "option=6,..." parameter. It could be
  "dhcp-option=6,10.20.0.2,8.8.8.8,8.8.4.4"
for example.

 Or you can configure NDS individually on each your node and/or tell dhclient use
locally configured values ( see supersede option in dhclient.conf).

I think the first variant is more preferable for you.

Can you help with this problem?

Provide an answer of your own, or ask Sam Stoelinga for more information if necessary.

To post a message you must log in.