DNS plays a very important role in making sure your deployed VMs are accessible, and if this is not configured correctly you can run into problems that can sometime be difficult to diagnose.

SovLabs modules make sure that no stale, duplication or orphaned DNS records exist which is great since we have all had those days where we are to lazy to unregister a VM from AD before we delete it, right!?

SovLabs also supports DNS integration with Infoblox, Bluecat and BT Diamond IP which is very helpful since these might be used for different departments and give you that flexibility to accommodate those scenarios.

For this blog I am focusing on using just the regular old Microsoft Active Directory.

The module has many features which can viewed on the website here, but some of the highlights are:

• Handles simple to complex globally distributed multi-zone, multi-site MS DNS environments
• Employs several methods to improve DNS data integrity and mitigate issues from stale, duplicate or orphaned DNS records, such as retry logic, record availability and DNS propagation/post validation checks
• DNS configurations are interchangeable between endpoint providers; avoid lock-in by easily adding additional DNS providers with other DNS modules from SovLabs
• Allows for independent configurations for forward and reverse records, if desired
• Supports up to 10 network interfaces per machine

 

Prerequisites:

1. Identify the Domain Controllers to be used, or if policy dictates no direct connections are allowed then identify a proxy server.
   • If using a proxy server then make sure the environment setup is complete by following these steps
2. If you are not using the SovLabs IPAM module, then you need to make you sure you set the DNS suffix within your network profiles that will be used.
3. Setup WinRM
   • WinRM must be enabled for SovLabs modules utilizing any Windows servers in the environment (for AD, DNS, IPAM, Puppet and etc.)
   • Follow these steps
4. Install AD Webservices on all the DC’s that will be used.
5. Verify NTP settings

 

Configuration:

1. Add Microsoft Endpoint
   1. This configuration was covered in my previous post which can be viewed here.
2. Add DNS configuration
   1. Select Catalog -> SovLabs vRA Extensibility
   2. 
   3. Click Request on “Add DNS Configuration – SovLabs Modules”
   4. 
   5. Enter Configuration label
      • Only AlphaNumeric characters, no spaces or special characters except: - and _
   6. Domains
      • Add all the domains for this DNS config
      • Enter name
      • Press Green plus sign
   7. Networks
      • Add all the networks for this DNS config
      • Enter name
      • Press Green plus sign
   8. DNS server type
      • MS DNS in my case
   9. DNS server endpoints
      • Select the one that was previously created
   10. Create A record = yes
   11. Create PTR record = yes
   12. Use a default server
       • Can specify this server if no match on domain and network.
   13. 
   14. Click Submit

 

Enable the module:

Now we need to enable the custom properties module on our blueprint

1. Click on Design -> Blueprint
2. Edit Blueprint
3. Click on the blueprint vSphere machine on the Design Canvas.
4. Click on properties tab
5. In the properties group section click +Add
6. Check the box for:
   • SovLabs-EnableLifecycleStubs
7. Click OK
8. Repeat these steps for all blueprints that should use this custom naming.

Now deploy a VM and watch the magic happen.  The provisioned VM will automatically attempt to register with Microsoft DNS only if the VM is in the configured domain and network defined for Microsoft DNS.

Disable the module:

If you have the DNS module installed but for some reason are not using it or need to disable it then following the steps below:

• If you do not have the DNS module configured, and try to deploy a catalog item, you will get an error like “Error: DNS Registeration could not find a DNS Configuration for the Hostname and/or IP of <servername> / 192.168.1.10 (Workflow:DNS machineBuilding / Add DNS (item10)#65)”

1. Click on Design -> Blueprint
2. Edit Blueprint
3. Click on the blueprint vSphere machine on the Design Canvas.
4. Click on properties tab
5. Click on Custom Properties tab
6. Click +New
   • Name = “SovLabs_DisableDNS”
   • Value = “true”
7. Click OK
8. Click Save
9. Repeat these steps for all blueprints that should use this custom naming.

Links:

http://docs.sovlabs.com/vRA7x/current.html#microsoft-dns

http://docs.sovlabs.com/vRA7x/current.html#infoblox-dns

http://docs.sovlabs.com/vRA7x/current.html#bluecat-dns

http://docs.sovlabs.com/vRA7x/current.html#bt-diamond-ip-dns