Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- A protection applies to one hosted-zone record name and type and covers every routing-policy record and set identifier for that pair. You can also reserve a name and type before a record exists.
- A CREATE, DELETE, or data-changing UPSERT for a protected record rejects the entire ChangeResourceRecordSets request, so none of its other records are applied. An UPSERT with identical values can succeed because it makes no change.
- Add and inspect protections from a hosted zone’s Protections tab. When creating a record with protection enabled, check for a warning that the record was created but the protection was not.
- Protection controls record changes; it does not change DNS answers and it is not an irrevocable lock. Restrict the route53:DeleteResourceRecordSetProtections permission.
What launched on November 12, and where is it available?
AWS announced Route 53 record set protection on November 12, 2026, in all commercial AWS Regions where public and private hosted zones are available. The reviewed announcement does not establish availability in other Regions or state a price for this feature; it does not support claims of China Region or GovCloud availability or free pricing.
Protection controls DNS record changes. It does not change DNS answers or guarantee service availability. It can help teams prevent accidental changes to critical A, MX or certificate-validation records, but cannot restore a record that was already changed or deleted.
Which records does a name-and-type protection cover?
A protection is identified by a hosted zone, record name and type. For example, protecting the A record for example.com covers every routing policy and set identifier—the identifier for a routing record—with that name and type. One protection covers all three weighted A records at that name; you cannot protect just one.
You can also create a protection before a record exists to reserve its name and type. No matching record can be created until the protection is removed. Protections can block changes you submit for NS or SOA records at the zone apex, the zone’s root name, but do not prevent Route 53 from updating those records as it manages the zone.
Add protection in the console and verify its state
Open Hosted zones in Route 53, select the target zone, then choose the Protections tab and Add protection. Enter a subdomain without the hosted-zone suffix, or leave the name blank for the zone apex. Each selected record type creates a separate protection.
An optional comment can contain up to 256 characters; Route 53 includes it in the error when it blocks a change. Check the name, type and comment on the Protections tab after adding it. For existing records, the Records tab’s Protection column also shows protection state, and Edit and Delete are disabled for protected records.
You can enable protection while creating a record, but Route 53 creates the record first and adds protection afterward. If the console warns that the record was created but is not protected, check the Protections tab and add the missing protection. A successful record creation alone does not prove protection succeeded.
Why does InvalidChangeBatch reject the entire batch?
If any CREATE, DELETE or data-changing UPSERT in a ChangeResourceRecordSets batch matches a protection, Route 53 rejects the whole request with InvalidChangeBatch (HTTP 400). None of its other records are changed. Compare the error’s full DNS name, type, optional set identifier and protection comment with every change in the batch.
Identify the blocked record before deciding whether to split or revise the planned change; do not assume the other records were updated. The AWS CLI, CloudFormation and SDKs follow the same rule. This rejection alone is not evidence of a network-proxy failure, and an UPSERT with identical contents can succeed because it makes no change.
Restore protection after an approved change
Confirm that the name, type and all matching routing records are within the approved change. Remove the exact protection and edit the record. If protection is still needed, add it again and verify the result on the Protections tab and in the Records tab’s Protection column.
Removing one protection makes every routing record with the same name and type changeable, so do not assess the scope using only one weighted record. You cannot edit a protection comment in place; changing it also requires deleting and recreating the protection.
Who can remove protection, and what limits remain?
Even a principal with broad Route 53 record-change permissions cannot directly change a protected record. A principal with route53:DeleteResourceRecordSetProtections permission can, however, remove protections in the hosted zone. This is not an irrevocable lock; restrict removal permission to the people or roles that need to manage protections.
A hosted zone cannot be deleted while any protection remains, including a protection reserving a name with no existing record. These are documented AWS behaviors; no AWS account was accessed or real DNS record changed for this article.
Sources
Frequently Asked Questions
How can automation avoid reading only the first page of protections?
ListResourceRecordSetProtections returns at most 300 protections per page. If the response includes NextToken, continue with that token in the same hosted zone. The AWS CLI automatically pages through results by default; check coverage separately if you deliberately limit pagination.
Where can I check who added or removed a protection?
AWS documents that creating, deleting and listing record set protections are logged in AWS CloudTrail. Review the relevant operations using your team’s existing audit permissions. No account logs were read for this article.