Hola! I do speak spanish , so if you think spanish will be quicker easier for you, feel free to send me an email
What I do understand from your mail is, at the first boot after vagrant provision the box, a working resolv.conf is there, and all good. Then, after the reboot, this resolv.conf change and doesn't work anymore for you. I don't think is going to be any different from virtualbox to vmware on your desktop, but is hard to know if you are on virtualbox/vmware/aws/openstack/docker/lxc :D For desktop, like vmware/virtualbox the eth0 is NAT, and will use the networking of your laptop, so if the laptop can reach the servers by name, the vm should. If the laptop can't then, the vm won't. Dirt fix will be do something like this: cp /etc/resolv.conf /etc/resolv.conf.ok echo 'cat /etc/resolv.conf.ok > /etc/resolv.conf' >> /etc/rc.local but is a hard ugly hack. if you share more information, I can try to assist to get a better solution and understand the problem. Saludos! Alvaro. On Mon, Jun 9, 2014 at 11:08 PM, Almudena Soblechero Garcia < [email protected]> wrote: > Good morning every body! > > > Im spanish, but i'm goint to tried write in english. > > > I'm workingwith Vagrant, and, i want to set up a dns server, but, when i > restart my vm, the resol.conf changes, and my DNS configuration, fail.... > > > There any solution, for that problem? > > > > I would like to use vagrant with a DNS server to work properly puppet. > > > Is this feasible? > > > rewards > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
