You can try with network offering with out DHCP and DNS services and control the guest instances to use AD as DNS/DHCP service provider. Please try out the steps outlined in [1].
[1] http://www.shapeblue.com/2012/05/10/using-the-api-for-advanced-network-mana gement/ On 23/04/13 2:12 AM, "David Ortiz" <dpor...@outlook.com> wrote: >Hello, > I am trying to setup a Windows AD server as a guest on my cloudstack >cluster, and join my other guests to the domain it is serving using >PowerBroker Identity Services Open. From what I am seeing, the virtual >router will block me from being able to perform nslookup or join the >domain using the domainjoin-cli command. If I modify /etc/resolv.conf to >point directly at my DC as the dns server, it can join the domain without >any issues. Unfortunately when I reboot, the dhcp setup with the virtual >router will point it back to the virtual router as the name server. I >also found that I could get nslookup (but not joining the domain) to work >by playing with the dnsmasq.conf settings on the virtual router a little >bit, which works until it is rebooted at which point they revert back to >what they had been originally. Is there a way to get the virtual router >to point guests at the domain controller as the DNS, or to set up the >dnsmasq to allow the AD joins to occur (and make those settings >persistent)? Or alternatively, would I be able to set up DHCP on the DC >and just circumvent the virtual router entirely? >Thanks, > David Ortiz
