Bulk templates

A bulk template is the shared mutation bulk_preview and bulk_submit apply to every domain a selector resolves to. The templateType decides which Jobs command runs and how each instance is addressed — by domain ID, by zone name, or by hostname.

Supported templates

The templateType is also the name of the Jobs command it runs.

templateType Instances addressed by
domain_update_bulk domain_id
dns_zone_create_bulk name
dns_zone_patch_rrsets_bulk zone_name
dns_zone_update_bulk name
domain_forward_create_bulk hostname
domain_forward_delete_bulk hostname
domain_forward_disable_bulk hostname
domain_forward_enable_bulk hostname
domain_forward_update_bulk hostname
email_forward_create_bulk hostname
email_forward_delete_bulk hostname
email_forward_disable_bulk hostname
email_forward_enable_bulk hostname
email_forward_update_bulk hostname

Not available through the bulk tools

The Jobs API accepts more bulk commands than these tools expose. They remain reachable by calling the API directly — see Domain commands — but not through a selector, for the reasons below.

Jobs command Why not
contact_create_bulk creates contacts, not domain-addressed, so there is nothing for a domain selector to resolve
dns_zone_patch_records_bulk superseded for MCP callers by dns_zone_patch_rrsets_bulk, which patches whole RRsets
dns_zone_restamp_vanity_ns_bulk vanity-nameserver restamping is an infrastructure operation, not a portfolio-wide edit
domain_create_bulk registers new domains, which the selector cannot name (it only resolves domains you already hold) and which is cost-bearing per name
domain_transfer_bulk transfers in domains held elsewhere, which the selector cannot name, and needs a per-domain auth code
parking_create_bulk parking is not exposed through the MCP tools yet
parking_delete_bulk parking is not exposed through the MCP tools yet
parking_disable_bulk parking is not exposed through the MCP tools yet
parking_enable_bulk parking is not exposed through the MCP tools yet