Hi all,

I am using Chef to deploy instances in an OpenStack environment. Therefore, since this OpenStack infrastructure is used as IaaS, I need to have the DHCP DNS server set, or I will lose all of the local network connectivity due to unresolved DNS requests.

I have an issue where as long as DHCP is putting that default nameserver (10.1.184.1) in /etc/resolv.conf, my own DNS server entries (which are currently using public IP addresses until I get VPN in place) will not resolve.

If I remove the DHCP nameserver entry, then my stuff resolves as I need it to, but then none of the OpenStack network connectivity works.

It doesn't matter if the DHCP DNS record is on the top or bottom in /etc/resolv.conf, it still won't let me resolv my DNS servers.

Thanks,
Kris

What server are you using internally? (10.1.184.1)

What it sounds like is happening is that your internal DNS server is set to disallow recursion (fetching DNS data from upstream sources when it receives a non-local request).

I can provide more guidance if I know what DNS daemon you're using.

1 members found this post helpful.

I actually found the answer last week and soarisguy, you are 100% correct in your answer. I ended up prepending my DNS servers in /etc/dhcp/dhclient.conf so they would be at the top in /etc/resolvconf/resolv.conf.d/head. Additionally, I added the following to /etc/bind/named.conf.options and now it all works fine (Later on I will replace `any` with specific networks/hosts:

recursion yes;
allow-recursion { any; };