Migrating from Your Own DNS Server or Another Company’s DNS Service to This Service

Use the following procedure to migrate zones being operated with a server other than servers for this service to this service.

[ Note ]

If DNSSEC is enabled at the migration source, make sure to disable DNSSEC before changing the name server.
If you migrate the DNS server without disabling DNSSEC, name resolution can no longer be executed with a cache DNS server for which DNSSEC verification is enabled.

For information on how to disable DNSSEC, contact the provider of the DNS service you are using. If you use the Domain Management Service, refer to the manual of "Domain Management Service."

[ Reference ]

Migration of domain management is not necessarily required for changing the DNS server.

Sign up for the Managed DNS Service.
Perform contract procedures for the Managed DNS Service. Refer to "Applications and Procedures" for more information.
Configure zone settings.
To configure zone settings, decide on an operational procedure and use the following pages as a reference according to your form of utilization.
You can perform the following operations even before the utilization start date (the zone status is "Unpublished").
- You can edit zones.
  - You can upload zone files that have been downloaded from the migration source’s server to this service.
    Replace the NS records of the zone files to upload with those of the Managed DNS Server.
- You can configure the zone proxy setting to this service from the primary name server that you have prepared or one from another company’s service. (Note that zone transfer is actually executed after the zone has been published.)
Correct zones with the migration source’s server.
1. If DNSSEC is enabled, disable it.
2. After the utilization start date, confirm that the zone status is "Published" on the control panel’s "Dashboard > Service List" screen.
3. Edit the zone files of the migration source’s server, delete the migration source’s server from the NS records, and add the Managed DNS Server.
  (Example) Configure the settings as shown below when the "example.com" zone is migrated and the old NS records are "ns1.example.jp" and "ns2.example.jp."
```
(Delete) @    86400 IN  NS ns1.example.jp.
(Delete)      86400 IN  NS ns2.example.jp.
(Add) @    86400 IN  NS ns-xxx.xxx.d-53.xxx.
(Add)      86400 IN  NS ns-xxx.xxx.d-53.xxx.
(Add)      86400 IN  NS ns-xxx.xxx.d-53.xxx.
```
  When the change operation has been completed, some DNS queries are set to be queries for this service (queries for the old server still exist).
Register the name server.
Use the procedure for "Registering and Changing Name Servers" to register the name server.
Once registration is complete, the number of queries to the migration source’s server will decrease, and within a few days you will have no access to migration source’s server.

[ Reference ]

There will be no queries to the migration source when both of TTL of the NS record prior to the change in procedure (3) and TTL of the NS record registered with the higher name server have passed.
By setting the TTL value to a short value in advance, you can switch DNS servers smoothly.
If switching NS cannot be performed in procedure (3) because of the migration source’s service specifications or other reasons, queries to the migration source will not be completely lost.
You can alleviate this effect by setting the parallel period to be a little longer without stopping the migration source’s server.

This completes the migration of the DNS server.
Stop the migration source’s server.
Delete (cancel) the zone from the migration source’s server.

List of published manuals

List of manuals for contractors