Hello,
Just to close the loop : after assigning public DNS servers to
dnsmasq_dns_server option in dhcp_agent.ini, both the internal and
external hostnames can be resolved. The DNS server in /etc/resolv.conf
is on the internal management subnet, which is not reachable from the
dhcp network na
Thanks for all the reply, as Paul said, the dnsmasq version doesn't
appear to be the issue here.
I also tested dns between 2 different VM subnets, instances can ping
each other across subnets, they can also reach dns server of the other
subnet. But hostname can't be resolved across subnets.
Al
You can get a newer dnsmasq version here:
http://pkgs.repoforge.org/dnsmasq/dnsmasq-2.65-1.el6.rfx.x86_64.rpm
Regards,
---
JuanFra
2013/11/14 Xin Zhao
> Hi Terry,
>
> I upgrade to version 2013.1.4 on all 3 hosts (controller/network/compute).
> Unfortunately that doesn't solve the DNS issue for
Hi Terry,
I upgrade to version 2013.1.4 on all 3 hosts
(controller/network/compute). Unfortunately that doesn't solve the DNS
issue for instances.
In the dhcp-agent.log, there is a message of:
WARNING [quantum.agent.linux.dhcp] FAILED VERSION REQUIREMENT FOR
DNSMASQ. DHCP AGENT MAY NOT RUN
> Hello,
>
> I have a multi-host grizzly RHEL6 install, using OVS. From the instance,
> I can ping external ips, but DNS resolv doesn't work, it only works for
> other instances on the VM network.
> If I do subnet-update to add public DNS server ips to the vm network,
> DNS resolv works for extern
