Creates a delegation set (a group of four name servers) that can be reused by multiple
hosted zones that were created by the same Amazon Web Services account.
You can also create a reusable delegation set that uses the four name servers that are
associated with an existing hosted zone. Specify the hosted zone ID in the
CreateReusableDelegationSet request.
You can't associate a reusable delegation set with a private hosted zone.
The process for migrating existing hosted zones to use a reusable delegation set is
comparable to the process for configuring white label name servers. You need to perform
the following steps:
Create a reusable delegation set.
Recreate hosted zones, and reduce the TTL to 60 seconds or less.
Recreate resource record sets in the new hosted zones.
Change the registrar's name servers to use the name servers for the new hosted
zones.
Monitor traffic for the website or application.
Change TTLs back to their original values.
If you want to migrate existing hosted zones to use a reusable delegation set, the
existing hosted zones can't use any of the name servers that are assigned to the
reusable delegation set. If one or more hosted zones do use one or more name servers
that are assigned to the reusable delegation set, you can do one of the
following:
For small numbers of hosted zones—up to a few hundred—it's
relatively easy to create reusable delegation sets until you get one that has
four name servers that don't overlap with any of the name servers in your hosted
zones.
For larger numbers of hosted zones, the easiest solution is to use more than
one reusable delegation set.
For larger numbers of hosted zones, you can also migrate hosted zones that
have overlapping name servers to hosted zones that don't have overlapping name
servers, then migrate the hosted zones again to use the reusable delegation
set.
Example
Use a bare-bones client and the command you need to make an API call.
You can create a hosted zone that has the same name as an existing hosted zone
(example.com is common), but there is a limit to the number of hosted zones that have
the same name. If you get this error, Amazon Route 53 has reached that limit. If you own
the domain name and Route 53 generates this error, contact Customer Support.
This operation can't be completed because the current account has reached the
limit on the resource you are trying to create. To request a higher limit, create a case with the Amazon Web Services Support
Center.
Creates a delegation set (a group of four name servers) that can be reused by multiple hosted zones that were created by the same Amazon Web Services account.
You can also create a reusable delegation set that uses the four name servers that are associated with an existing hosted zone. Specify the hosted zone ID in the
CreateReusableDelegationSet
request.You can't associate a reusable delegation set with a private hosted zone.
For information about using a reusable delegation set to configure white label name servers, see Configuring White Label Name Servers.
The process for migrating existing hosted zones to use a reusable delegation set is comparable to the process for configuring white label name servers. You need to perform the following steps:
Create a reusable delegation set.
Recreate hosted zones, and reduce the TTL to 60 seconds or less.
Recreate resource record sets in the new hosted zones.
Change the registrar's name servers to use the name servers for the new hosted zones.
Monitor traffic for the website or application.
Change TTLs back to their original values.
If you want to migrate existing hosted zones to use a reusable delegation set, the existing hosted zones can't use any of the name servers that are assigned to the reusable delegation set. If one or more hosted zones do use one or more name servers that are assigned to the reusable delegation set, you can do one of the following:
For small numbers of hosted zones—up to a few hundred—it's relatively easy to create reusable delegation sets until you get one that has four name servers that don't overlap with any of the name servers in your hosted zones.
For larger numbers of hosted zones, the easiest solution is to use more than one reusable delegation set.
For larger numbers of hosted zones, you can also migrate hosted zones that have overlapping name servers to hosted zones that don't have overlapping name servers, then migrate the hosted zones again to use the reusable delegation set.
Example
Use a bare-bones client and the command you need to make an API call.
Param
CreateReusableDelegationSetCommandInput
Returns
CreateReusableDelegationSetCommandOutput
See
input
shape.response
shape.config
shape.Throws
DelegationSetAlreadyCreated (client fault)
A delegation set with the same owner and caller reference combination has already been created.
Throws
DelegationSetAlreadyReusable (client fault)
The specified delegation set has already been marked as reusable.
Throws
DelegationSetNotAvailable (client fault)
You can create a hosted zone that has the same name as an existing hosted zone (example.com is common), but there is a limit to the number of hosted zones that have the same name. If you get this error, Amazon Route 53 has reached that limit. If you own the domain name and Route 53 generates this error, contact Customer Support.
Throws
HostedZoneNotFound (client fault)
The specified HostedZone can't be found.
Throws
InvalidArgument (client fault)
Parameter name is not valid.
Throws
InvalidInput (client fault)
The input is not valid.
Throws
LimitsExceeded (client fault)
This operation can't be completed because the current account has reached the limit on the resource you are trying to create. To request a higher limit, create a case with the Amazon Web Services Support Center.
Throws
Route53ServiceException
Base exception class for all service exceptions from Route53 service.