A record set keeps several related DNS records together so you can reuse a setup. It is helpful for a repeated hosting arrangement or a provider that asks for several verification records. A set is a saved recipe; changing the recipe later does not automatically change domains that used it previously.
IN THIS ARTICLE
01 Create your own set
- Open a domain you can manage and select Bulk & setup.
- In the record-set area, choose New record set.
- Give the set a clear name describing its purpose, such as the hosting environment or mail service.
- Add each record using the type, name, value, TTL and any type-specific fields shown by the editor.
- Use the real values for your intended setup. Do not paste a sample IP address or another customer's verification token.
- Save the set and reopen it to check the complete record list.
02 Apply the set to a domain
Select the intended domain and choose the saved set. Some packages also offer provider-prepared sets. Those are available only where Nabtech has made them part of the package. Preview the result before confirming, especially when an existing name and type already have records.
Check whether the available apply option merges the set with the zone or replaces other records. Replacement can remove working services. Keep records outside the intended change, such as MX, DKIM selectors, DMARC, certificate validation and separate application subdomains. Where the preview shows a conflict, resolve the intended final record arrangement rather than applying several conflicting templates.
Which values must I change before reusing a DNS record set?
Your private sets belong to your client account. A TXT verification value or DKIM public key issued for one service may not be valid for another domain. Similarly, a CNAME pointing to an old application account remains wrong even if the record is syntactically valid. Review those values each time you reuse a set.
03 Verify and maintain
Wait for the resulting DNS change to be applied and verified. Then confirm the records in the zone and complete the external provider's verification step if applicable. Rename, duplicate or edit a private set when your setup changes. Removing the set from your saved collection does not by itself withdraw records already published in a zone. Remove those records separately only when the service no longer needs them.