Implement the following stages carefully:
- Stage 0: Provision your zones using Edge DNS on Control Center. This allows your zone information to come to Akamai. For secondary zones, verify that Edge DNS is updating your zones successfully. (See “Testing”.)
- Stage 1: Delegate your zones to a subset of your original servers and some Akamai servers. To retrieve the list of Akamai name servers, click Authoritative name servers on the Zone list page.
- Stage 2: Delegate your zones to all six Akamai servers (and some or all of your original servers, if desired).
To safely complete Stages 1 and 2, follow the steps in this topic.
Update the relevant NS (name server)
records in your zone file. (For Stage 1, the records should consist of your original
servers and some Akamai servers. For Stage 2, the records should consist
of all six Akamai servers and zero or more of your original servers.)
CAUTION: Allow these zone updates to propagate to the new and the original servers. Your original servers keep receiving traffic, and since they’ll most likely supply authority information when providing answers, they might refresh authority information in client name server caches. Therefore, those client name servers might never learn of the new authorities unless you allow your original servers to provide the new authorities to result in a smooth transition.
It’s important to realize that once your original servers start serving the new NS records, some traffic reaches Akamai servers.
- Ensure that the NS records have propagated to Akamai name servers. You can view the oldest start of authority serial number for your zone on the name servers using Control Center. See View zone transfer status for more information.
- Provide your registrar with the names of the Akamai name servers that you included in your zone file. Zone changes with the registrar normally take about five minutes to propagate to the top-level domain name servers. At this point, end users routinely start making requests to the Akamai name servers.