Use bulk DNS changes across one or several zones

Inside one domain, Bulk & setup works with that zone. In the account-wide DNS view, bulk management can act across the zones you are entitled to manage. Only select the domains that should receive this specific change. Similar domain names are not a reason to assume they use the same hosting or email service.

1. Open Bulk & setup or the account-wide bulk-management view.
2. Select the required zone or zones, where the page offers a zone selector.
3. Choose the available operation, such as replacing a matching address, changing TTL or adding the same record.
4. Enter a precise match. For an address replacement, use the old address you intend to retire, rather than a broad text fragment that might match unrelated records.
5. Generate the preview and read the affected records, additions and removals.
6. Check that MX targets, verification TXT records, protected entries and unrelated subdomains are unchanged unless you explicitly intended to change them.
7. Confirm the reviewed operation and follow its progress.

Zones are checked against their own ownership, package, provider and lock state. A multi-zone request can encounter a zone that is read-only, full, in another operation or incompatible with the chosen record type. Read the result for each affected zone. Do not infer that every domain changed because one domain completed.

When correcting a failed subset, first refresh its current records. Retrying a broad operation without reviewing completed work can produce duplicates or reverse a deliberate difference between sites. Preserve the preview or operation reference so support can identify the exact request.

After provider application finishes, check the relevant public DNS answers for a representative domain from each configuration group and for every reported failure. Test the service behind the record as well. A valid A record proves an address was published; it does not prove that the new server has the right website or a working certificate. DNS caches may retain old answers until their previous TTL expires.

• Back up and restore DNS records
• Create and apply reusable DNS record sets
• Check DNS propagation and find the source of an old answer
• Read DNS history and schedule a record change