That should not be necessary. The DNS server in the router is a forwarder: 1. If the target of the DNS resolve is for a VM it has served DHCP to, it responds with the entry 2. If not, it forwards it to the 'zone' dns server.
Or, you can set use.external.dns to 'true', restart the management server and restart (from the api/ui) the virtual router. But if you do, you won't get #1. On 11/7/12 3:12 PM, "Alex Huang" <alex.hu...@citrix.com> wrote: >In 4.0, what I would do is this. > >- Write a plugin. >- Listen to vm start events. >- On router vm start, ssh into the router vm and change the resolv.conf > >In the next release, Murali have added proper external event system then >you don't even need to do this via a plugin. > >--Alex > >-----Original Message----- >From: Caleb Call [mailto:calebc...@me.com] >Sent: Wednesday, November 07, 2012 3:06 PM >To: cloudstack-users@incubator.apache.org >Subject: Re: alter resolv.conf nameservers on linux > >Good question, I've been meaning to ask this same thing and keep >forgetting to. I think I've read that you have to edit the config on the >router vm, but that doesn't persist a reboot of the router vm. Is there >a better way to do this? > > >On Nov 7, 2012, at 3:18 PM, "Musayev, Ilya" <imusa...@webmd.net> wrote: > >> How would I pass on my nameservers in resolv.conf of an instance, >>instead of router vms IP? >> >> As of now, my nameserver is set to ip address of router vm. >> >> >> Thanks >> ilya >
