Doing quantum subnet-update sub1 --dns_nameservers 8.8.4.4 8.8.8.8 works. BTW from horizon you can pass one dns also. Thanks guys Paras. On Fri, May 17, 2013 at 3:47 PM, Darragh O'Reilly < dara2002-openstack at yahoo.com> wrote: > Hi, > > I reckon this is because dnsmasq is isolated in the dhcp namespace. You > can use > DHCP to push out a specific nameserver: > > $ quantum subnet-update sub1 --dns_nameservers 8.8.4.4 8.8.8.8 > > I can't seem to figure out the syntax to pass just one (list=false is not > working). Or you could use Horizon instead. Anyway the DHCP agent should > ensure > that it is pushed out to the instance's resolv.conf or whatever. > > Darragh. > > >________________________________ > > From: Paras pradhan <pradhanparas at gmail.com> > >To: openstack <openstack at lists.launchpad.net> > >Sent: Friday, 17 May 2013, 20:08 > >Subject: [Openstack] instance dns issue > > > > > > > >Hi, > > > > > >My instances can ping the ips but not using dns. The resolv.conf gets > populated by the private instance network dns ip (10.0.0.2, from > 10.0.0.0/24) . I can ping the dns ip but dns resolv is not working. What > might be the issue? > > > > > >I am on quantum and grizzly in 12.04 lts. > > > > > >Thanks > >Paras. > >_______________________________________________ > >Mailing list: https://launchpad.net/~openstack > >Post to : openstack at lists.launchpad.net > >Unsubscribe : https://launchpad.net/~openstack > >More help : https://help.launchpad.net/ListHelp > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130517/567bea7d/attachment.html>