I briefly remember having similar problems at some point, but do not recall details as version nor the solution.
1) Does it work if you restart dnsmasq on the VR? 2) is the VR able to do outgoing dns requests? 3) anything in syslog/dnsmasq logs? 4) any egress rules in place? Erik Den torsdag 26. mars 2015 skrev cs user <acldstk...@gmail.com> følgende: > Hi All, > > We have upgraded from 4.3 to 4.4.2. > > After some issues with starting the systemvm's, the virtual routers no > longer responding to dns requests from the vm's which we start (or existing > ones). > > We have disabled the firewall on the virtual routers and ran tcpdump on > them but we can't see any inbound traffic on port 53 (udp or tcp). If we > log onto the virtual routers and dig locally against eth0 and the alias on > eth0 both of these return fine with the correct IP. > > This is using Xenserver 6.1 as the host. > > Has anyone come across this before? dhcp lookups appear to be working fine. > Is there a firewall rule in place on the router vm's (other than iptables), > similar to the security groups which are applied by Xen, which is > preventing these requests from hitting the routers? > > Many thanks for any help. >
