I had the same problem, and still have. Look at it:
https://lists.launchpad.net/openstack/msg23360.html
Rusty
On Fri, May 17, 2013 at 11:27 PM, Paras pradhan wrote:
> 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.
>
> Tha
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-openst...@yahoo.com> wrote:
> Hi,
>
> I reckon this is because dnsmasq is isolated in the dhcp na
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 Horizo
Hmm. telnet to 53 is not working.
Paras.
On Fri, May 17, 2013 at 3:20 PM, Ashok Kumaran wrote:
> Can you telnet to port 53 of local DNS ip from your instance (IP in your
> resolv.conf) ? If its not working then you might need to check your local
> quantum dnsmasq settings.
>
>
> On Sat, May 18
Can you telnet to port 53 of local DNS ip from your instance (IP in your
resolv.conf) ? If its not working then you might need to check your local
quantum dnsmasq settings.
On Sat, May 18, 2013 at 1:45 AM, Paras pradhan wrote:
> Thanks. Yes I got the concept but something is not working. I can'
Thanks. Yes I got the concept but something is not working. I can't resolv
the hosts from my instances.
Thanks
Paras.
On Fri, May 17, 2013 at 3:10 PM, Ashok Kumaran wrote:
> It will not populate the external DNS ip in your resolv.conf . Instead
> the external DNS will be used by the local quan
It will not populate the external DNS ip in your resolv.conf . Instead the
external DNS will be used by the local quantum dnsmasq for the name
resolution purpose.
For an instance lets say that your network node has a DNS ip of some
xx.xx.xx.xx in its resolv.conf . By adding the same IP to the
dh
So adding dnsmasq_dns_server= "external DNS IP" should populate the
resolv.conf of my instances with the externel DNS IP?
I did that but still seeing the same ip on resolv.conf.
Paras.
On Fri, May 17, 2013 at 2:17 PM, Ashok Kumaran wrote:
> I am assuming that you have a DNS externally and you
I am assuming that you have a DNS externally and you want the instances to
use that DNS. If this is the requirement then
you will have to add dnsmasq_dns_server= "external DNS IP" in your
/etc/quantum/dhcp_agent.ini.Now your launched instances(VM's) can use
external DNS through quantum dnsmasq.
Pl
9 matches
Mail list logo
