openstack team mailing list archive

[Ashok Kumaran <ashokkumaran.b@xxxxxxxxx>]

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
dhcp_agent.ini you can make your instances to use the same DNS. I hope you
got the concept


On Sat, May 18, 2013 at 1:32 AM, Paras pradhan <pradhanparas@xxxxxxxxx>wrote:

> 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 <ashokkumaran.b@xxxxxxxxx>wrote:
>
>> 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.
>>
>> Please let us know if you have some other requirement.
>>
>> -Ashok
>>
>>
>> On Sat, May 18, 2013 at 12:38 AM, Paras pradhan <pradhanparas@xxxxxxxxx>wrote:
>>
>>> 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@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Regds,
>>
>> Ashok ,
>> Delivery Consultant,
>> HP.
>>
>
>


-- 
Regds,

Ashok ,
Delivery Consultant,
HP.