Use an authorized self-managed or server-administrator account. Export or record the existing template and representative zones. Identify customer-specific mail, verification and external-service records that must remain intact. Confirm which zones are publicly authoritative on this server.

1. Open Tools & Settings > DNS Settings and review the server-wide template.
2. Modify the required record using the supported domain or address placeholders. Avoid inserting a single customer hostname where a template variable is intended.
3. Save the template and inspect a test domain created under the new defaults. Verify generated names, addresses and record syntax.
4. If existing zones need the change, use the supported template-application workflow deliberately. On Linux, the synchronization distinguishes template-derived records from user-modified records; review the displayed scope rather than assuming every zone will become identical.
5. Test a selected representative zone first where possible, then apply the intended wider scope during a controlled change window. Keep the original template and zone exports for recovery.

Compare authoritative answers for test and existing domains. Check website, mail and validation records and review any synchronization errors. Confirm new domains inherit the desired defaults without introducing stale provider-specific values.

If an existing record does not change, it may have been customized or the zone may be treated as modified after migration or restoration. Investigate its provenance before forcing an overwrite. Reverting a template does not necessarily reverse every already applied zone change, so use recorded per-zone values for precise recovery.

• Knowing when Plesk DNS changes control public records
• Enabling DNSSEC for a Plesk-managed zone
• Migrating a subscription with Plesk Migrator
• Connecting a Plesk application to Microsoft SQL Server

• Plesk: DNS Settings