A package's default record set creates starting records automatically. Offered sets are additional choices shown to eligible customers. Customers may also maintain their own private sets when their permissions allow it. These three uses should have clear names so the interface does not suggest that every template is applied automatically.

1. Create and test the administrator record set under Record sets.
2. Open the relevant DNS package and locate the customer record-set selection below the default-set controls.
3. Select only the sets appropriate for that package. Check that the package also allows customers to use record sets.
4. Save, then sign in as a qualifying test customer and open Bulk & setup for a zone.
5. Confirm the offered set appears, its preview resolves correctly and the customer can apply it without changing the shared administrator template.

Give each set a description that explains the intended service and any required customer input. Preview on a representative zone to see which records will be added, updated or removed. Teach customers to choose merge or replace based on the actual result shown, rather than assuming both options preserve unrelated services.

Protected and provider-managed records remain subject to policy. A set cannot bypass a package limit or add unsupported record types. If a template requires a unique verification token or DKIM value, it must not distribute a sample or another customer's token as a universal record.

Review templates when the target service changes its DNS requirements. Updating the offered set does not silently repair zones where an earlier version was already applied. For a required customer change, provide a clear migration guide and a reviewed update workflow.

Removing a set from the package's choices prevents future selection there. It does not remove records previously installed in customer zones. Keep the old configuration documented until affected services have been checked, particularly when replacing email records.

If a customer cannot see a set, verify the resolved package, the record-set permission and the offered-set selection before investigating the DNS provider.

• Create DNS record sets that become package defaults
• Build a DNS package for hosting products, addons and domain TLDs
• Create and apply reusable DNS record sets
• Import DNS records from another provider