A CloudStack account can be associated with a network domain.
Instances created within this account will have its DNS suffix automatically set to the configured network domain. CloudStack admins can create new domains from the ‘Domains > Add New Domain’ tab. DNS domains which are associated with isolated networks are not queriable from the Internet directly. This is because, the virtual router that provides the DNS services is not known to the end users.
Instead, we can expose the DNS services provided by the virtual router to the Internet for a specific domain by creating a dedicated VM instance which acts as a forwarding DNS server.
In this example, we create a new CloudStack domain called “demo.local” and allow external DNS lookups.
Continue reading Forward DNS Queries To CloudStack Internal Isolated Network
Motty Cruz, recently reported having issues installing and running FreeBSD on his CloudStack 4.2.1/CentOS 6.5 KVM environment.
My environment is very similar, except that I prefer to run FreeBSD on XenServer instead of KVM. FreeBSD 10 and later versions have XENHVM support possibly making Xen a better platform for FreeBSD.
So does FreeBSD have issues running on Apache CloudStack 4.2.1 and CentOS 6.5 KVM hypervisors?
Continue reading FreeBSD 10 On CloudStack + KVM
If you had 3xQuad port network controllers having a total of 12 usable ports, your network bonding+bridging could look as below:
On CentOS/RedHat, the network settings would be as below:
Continue reading Network Bonding With CloudStack and Linux KVM