DNS module best practices

Best practices for OneFuse DNS validation when used with Naming, IPAM, and standalone

  2 minute read  

The CloudBolt OneFuse integration platform offers a DNS Module that can be leveraged to provide enterprise grade DNS registration for creating host, A, and PTR records with support for Infoblox, BlueCat, Men & Mice, and Microsoft DNS services with more to come.

The OneFuse DNS module allows for both pre and post validation of DNS records to ensure names are unique before they are created and resolvable after creation.

Resources

For additional information regarding OneFuse DNS, refer to the following documentation:

Prerequisites

For each DNS Policy you create, you will need:

  1. A DNS Endpoint
  2. Credentials with permissions to create DNS records

Best practice for DNS validation

With OneFuse Naming and IPAM modules

If you are using the OneFuse Naming and IPAM Modules with the OneFuse DNS Module, and you are using a DNS naming validator with the Naming module, it is best practice not to pre-validate the record using DNS.

Naming:

Validate the name using the Naming module instead of the DNS module if both are in use. This allows OneFuse to generate a new name, revalidate, and continue.

If validation is performed at the DNS module and the validation fails, it will fail the request and the resulting build.

IPAM:

The OneFuse IPAM module performs a validation ensuring the IP address is not already in DNS.

Always perform a post-validation to ensure the created record can be resolved. This will ensure any automation tasks that require DNS resolution after the DNS record is created will resolve the record.

Without OneFuse Naming and/or IPAM modules

If you are not utilizing both the OneFuse Naming and IPAM modules, it is best practice to use DNS pre-validation to ensure there is no duplicate record for the entry you are about to create.

Post-validation sleep seconds

Set the post-validation sleep seconds to a time appropriate for your environment. Pad the value by 30–60 seconds if you regularly experience delays in DNS replication, to ensure builds do not fail due to latency or slow replication during peak activity.

Outcomes

Use best practices to validate DNS records and ensure that builds succeed.