Hello,
We started facing strange issue with cloudstack VM. where all the VMs in
one particular tenant are not able to resolve DNS. since we are using
advanced networking we have tried to reboot virtual router and other DNS
services. still that particular tenant is not able to resolve the DNS.
Hi Tejas,
“DNS server is currently hosted in public network subnet which is being used by
all the tenants”.
Is this DNS server hosted directly on the public network and externally to
CloudStack, or is it hosted on a CloudStack isolated/VPC network with DNS
services port forwarded to the public
The other thing to check is that you haven't specified your external DNS as
internal DNS within the advanced zone settings. I know from experience that
CloudStack will place a static route into the VR to force traffic out the
internal interface if you specify internal dns, since the default rout
Hi Dag,
Thanks for quick response.
As mentioned below , we do not have Packages for 4.10 when Management server
OS is Centos 6.x. If anyone has built at source then that will be helpful.
Also in Centos 7 Package list we do not have packages for 4.9.3 Build. When we
followed the document
Hi Anil,
If you check our own repositories the RPMs are up there -
http://packages.shapeblue.com/cloudstack/upstream/
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
From: "Barbadekar, Anil"
Reply-To: "[email protected]"
Date: Friday, 6 October 2017 at 15:38
To: "[email protected]
Hello Dag Sonstebo,
First of all thanks for the detailed reply.
Just wanted to update you on following.
1) Any reason why you aren’t just letting the clients use the VR for DNS
forwarding, rather than going direct?
--> in fact, we are letting clients to use VR for DNS forwarding . All of
