Tuesday, May 10, 2016

Touchy DNS in Kitchen/Vagrant VM's?

TL; DR

Add to your drive section in .kitchen.yml

1
2
  customize:
    natdnshostresolver1: "on"

Symptom

I often work remotely. It's a beautiful thing; however, "Thar be dragons!" Does your cookbook need private DNS? Resources behind the firewall? Well, let's connect to VPN. WooHoo... Wait... The chef-client install failed. It can't get to the internet? WHAT? 

Solution

My VPN client has split tunneling DNS and split tunnel networking. So... How do you working around it? Tell kitchen to tell vagrant to use your host workstation as the DNS server.





No comments:

Post a Comment