Overview
In this how to, we will explore some basic scenarios around configuring the SovLabs DNS module and how you can even disable DNS if required.
Scenarios
1 Single IPAM / DNS setup and standard deployment
- Configure a single domain for DNS using Infoblox
2 Single IPAM / DNS setup and setting DNS to Disabled
- Configure a blueprint with "SovLabs_DisableDNS = true"to disable DNS for that blueprint
3 Single IPAM / DNS setup and dynamically Enable/Disable DNS
- Dynamically set "SovLabs_DisableDNS = true" on your blueprint
4 Multi Domain across different DNS providers
- Configure a blueprint to select the Domain
- Based on domain, IPAM profile and DNS will trigger the creation of records.
- This is a mix between Dynamic IPAM profile selection and DNS selection.
Considerations
- Have licensed the appropriate modules for DNS/IPAM
- Have configured service accounts to have the appropriate access to DNS
- Have met all pre reqs for your chosen DNS provider
- Have configured Endpoints for your IPAM/DNS provider
- Have licensed SovLabs Property Toolkit for more advance features
Procedure
Scenario 1
- In your catalog (1) earch for Add DNS Configuration (2) and click on Request within Add DNS Configuration - SovLabs Modules (3)
- End a Configuration Label that is meaningful
- Type in the domain to use (1) and click the green plus (2)
- In Networks, Enter the IP Address range you are using from your IPAM (1) and click on the green plus (2)
- In the DNS server type, drop down and select your DNS provider, in this example, we will be using Infoblox
- In the DNS server endpoint, place a check next to the appropriate endpoint you had already configured
- Place checks next to all that may apply to create an A record / PTR Record (1), You can opt to create a Host record (2), Leave use as a default server unchecked in this example (3)
- Click on Submit
- You do not have to add anything to your blueprint apart from your IPAM profile. DNS will be picked up automatically based on the IP range and DNS zone in your IPAM profile
- You can confirm in vRO that the DNS module has run by looking at SovLabs → DNS → DNS machineBuilding.
Scenario 2
- In your blueprint , go to Properties (1), Custom Properties (2) and click on New (3)
- In the Name area (1) type in SovLabs_DisableDNS and in the Value (2), type True then click OK (3)
- Click on Finish
- You can confirm in vRO that the DNS module has skipped the DNS creation by looking at SovLabs → DNS → DNS machineBuilding.
Scenario 3
- Go to Administration (1) → Property Dictionary (2) → Property Definitions (3) and click on New (4)
- Provide the property with a meaningful name, in this instance, we want to set true/false against the SovLabs_DisableDNS value
- Provide a label that will be shown on your blueprint
- Set the Data type to Boolean
- Select the Display type to Yes/No
- Click on OK
- Go back to your blueprint and click on Properties (1) → Customer Properties (2) → and create a new (3)
- In the name field, start typing the Property Definition we created and select this in the drop down
- Place a check in the Show in Request
- Click on OK
- Click on Finish
- Now deploy your blueprint, you will see an extra value to enable or disable DNS
- If you deploy your blueprint and select each option, you will see in vRO one will provision DNS and the other Will skip
- Disabled Example
- Enabled Example
- Disabled Example
Scenario 4
- In vRA click on Administration (1) → Property Dictionary (2) → Property Definitions (3) → New (4)
- Enter a name for the Domain Selection
- Enter a Label that will be displayed on your Blueprint
- Enter the data type (1) as String and Required (2) should be Yes
- Display as DropDown (1) and Values (2) as static
- Enter in the Name (1) and value (2) as required.. In this example, I am selecting the IPAM Profiles that relate to each domain. This will allow you to dynamically provision to each different domain
- Click on OK
- Click on Administration (1) → Property Dictionary (2) → Property Groups (3) , Scroll down and find a group starting with SovLabs-IPAMProfile_<tenant__<IPAM Profile Name> (4) and click Copy (5)
- Change the Last section after your <Tenant>_ and make it meaningful to this scenario
- Change the description to reflect the new name
- In the properties, Look for SovLabs_IPAMProfile_nic0 and change the value to be templated, this should be the name of the Property Definition you created
- Click on OK
- Go back to your blueprint and click on Properties (1) → Custom Properties (2) → and click on New (3)
- Under name, enter the name of the property definition you created earlier
- Place a check in Show in request
- Click on OK
- Click on Property Groups (1) → then click Add (2)
- Search for your SovLabs_IPAMProfile-<Tenant>_<IPAMProfileName> (1) and place a check next to it, then click on OK (2)
NOTE: Please make sure you only have 1 IPAM Profile attached to your blueprint - Click on Finish
- Now when you deploy your blueprint, you will have a drop down for your domain choice, this will now deploy to your selected IPAM / DNS profile
- You can confirm this in vRO workflows for DNS, you will see which DNS name / Domain your Machine has built with
Additional information
Sovlabs IPAM / DNS Module information: http://docs.sovlabs.com/latest/vRA/7.6/modules/#endpoint-integrations
0 Comments