Domains

Bulk actions on domains

How to change auto-renew, reminders, the transfer lock or name servers for many domains at once, stop a batch and roll the changes back.

If you have many domains, you don't have to open each one. Select them in the list and run one action for all of them. This is called a batch.

What you can do in a batch

  • turn auto-renew on or off;
  • remind or not remind about the term;
  • not renew, that is, let the domains go;
  • set the transfer lock (a batch cannot remove the lock: that is done in each domain's card);
  • change name servers.

One batch holds up to 1000 domains unless another limit has been set for you.

Step by step

  1. Open Domains → All domains and tick the domains you need.
  2. Actions appear above the table. Choose the one you need.
  3. We build a plan and check every domain before the start: "can" or "already so, nothing will change". Nothing has been changed yet.
  4. Review the plan in Domains → Bulk actions. If all is well, click Start. If not, Cancel plan.
  5. The batch runs one domain at a time. You can stop it between domains with Stop.
  6. For each domain you see the result: changed, no change, failed.

Actions that can lead to losing a domain (turning off auto-renew or reminders, letting go, changing name servers) need a fresh confirmation with a code from the app or a passkey. All organization owners receive a letter about turning off auto-renew and changing name servers.

Batch states

StateWhat it means
Waiting to startThe plan is checked, nothing changed yet.
RunningDomains are processed one at a time.
StoppedThe batch was stopped, the remaining domains were not started.
FinishedAll domains are processed.
Rolled backThe changes were undone.
Plan cancelledNothing was changed.

Rollback and retry

  • Retry failed: queues the domains where it did not work.
  • Roll back: returns the previous state. A finished batch can be rolled back for 30 days. The transfer lock has no rollback.
  • The "Bulk actions" page keeps the last 50 batches.

If it didn't work

What you seeWhat to do
"Failed" next to a domainOpen the batch and read the reason, then click Retry failed.
The domain is frozen during a disputeIt is skipped: nothing changes while the dispute lasts.
The action is unavailableEach action needs its own role: auto-renew and letting go need the right to pay, locks and name servers need separate rights.
A bulk name server change will not start after access recoveryName servers cannot be changed for 72 hours after access recovery.

This page in Markdown