Transfer domains from DNS hosting (legacy) to DNS hosting (actual)

Last update: November 19 2024

Transfer domains from DNS hosting (legacy) to DNS hosting (actual)

For your information

We've released new version of DNS hosting (actual) and stop supporting and developing legacy. Domains and resource records in DNS hosting (legacy) continue to work, we will warn you in advance about their discontinuation.

We recommend migrating domains and resource records to DNS hosting (actual) now to avoid disruption of sites when DNS hosting (legacy) goes down.

Domain transfers happen without pausing DNS operations. You create a copy of the data from DNS hosting (legacy) in DNS hosting (actual), and then delegate record management to the authoritative servers in DNS hosting (actual). The migration can take up to 72 hours, during which time the records will continue to be served from the authoritative DNS hosting (legacy) servers.

If a domain in DNS hosting (legacy) only has NS and SOA records, it will not be migrated to DNS hosting (actual). If you need to migrate such a domain, you need to add it through the control panel.

All domains from DNS hosting (legacy) are migrated to one project.

You can transfer domains:

• through the control panel;
• through octoDNS.

After the migration to DNS hosting (actual), you can transfer the domain zone to another project.

Transfer a domain through the control panel⁠

1. Transfer the data.
2. Delegate the domain to DNS hosting (actual).

Transfer data⁠

1. In control panel go to DNS → Domain zones.

2. Copy the ID of the destination project to which you want to transfer zones. To do this, open the projects menu (the name of the current project) and in the line of the required project press .

3. Go to the section Network services → DNS hosting.

4. Click Zone copying.

5. Insert the recipient project ID and click Copy. When the window closes, copying is complete.

6. In control panel go to DNS → Domain zones.

7. Make sure that you are in the project to which you have moved the data. To do this, open the projects menu (name of the current project) and select the desired project.

8. Make sure that the transferred domains are displayed in the zone list and that each zone's page displays the transferred domain records.

   Resource records of the same type are displayed as a group of records. NS and SOA resource records are not migrated, they will be automatically created in DNS hosting (actual) with default values:

   • NS — a.ns.selectel.ru., b.ns.selectel.ru., c.ns.selectel.ru., d.ns.selectel.ru.
   • SOA IS. a.ns.selectel.ru. support.selectel.ru. <zone_serial_number> 10800 3600 604800 60where <zone_serial_number> — zone serial number, which changes when the zone is updated and signals to the caching servers that records need to be cached again.

   If the data has been migrated incorrectly or incompletely, file a ticket.

Delegate domain to DNS hosting (actual)⁠

If you have transferred multiple domains, you need to delegate each domain.

1. Go to the control panel of the domain registrar where your domain is registered.
2. In the NS records, replace the values with the DNS hosting (actual) NS servers: a.ns.selectel.ru, b.ns.selectel.ru, c.ns.selectel.ru, d.ns.selectel.ru. Specify each server in a separate entry.
3. Wait for the migrated resource records to propagate to the DNS servers. Propagation can take up to 72 hours.
4. Optional: check the records on authoritative servers. Record migration can take up to 72 hours, during which time records will continue to be served from authoritative DNS hosting servers (legacy): ns1.selectel.ru, ns2.selectel.ru, ns3.selectel.ru, ns4.selectel.ru.

Transfer domain via octoDNS⁠

1. Install octoDNS.
2. Transfer the data.
3. Delegate the domain to DNS hosting (actual).

Install octoDNS⁠

1. Install Python 3, virtualenv, and pip3:

   Linux

   sudo apt-get update
   sudo apt-get install python3 virtualenv
   sudo apt-get install python3-pip

   macOS

   brew install python3
   brew install virtualenv

2. Create a directory to work with octoDNS:

   mkdir ~/octodns

3. Go to the directory ~/octodns:

   cd ~/octodns

4. Create a virtual environment to work with octoDNS:

   virtualenv env

5. Activate the virtual environment:

   source env/bin/activate

6. Install octoDNS in a virtual environment:

   pip3 install octodns

7. Check that the package has installed correctly:

   octodns-sync --version

   The response will show the installed version of octoDNS, for example:

   octoDNS 1.4.0

8. Set Selectel provider for octoDNS:

   pip3 install octodns_selectel

9. Check that the Selectel provider has been installed correctly:

   pip3 list | grep octodns-selectel

   The response will show the installed version of the provider, for example:

   octodns_selectel 0.99.1

   The minimum Selectel provider version for portability is 0.99.1.

Transfer data⁠

1. Go to the directory ~/octodns:

   cd ~/octodns

2. Create a file migration_config.yaml:

   nano migration_config.yaml

3. Copy the contents into the file:

   ---
   processors:
     no-root-ns:
       class: octodns.processor.filter.IgnoreRootNsFilter
   
   providers:
     selectel_legacy:
       class: octodns_selectel.SelectelProviderLegacy
       token: <selectel_token>
     selectel:
       class: octodns_selectel.SelectelProvider
       token: <keystone_token>
   
   zones:
       <example.com.>:
           sources:
           - selectel_legacy
           processors:
           - no-root-ns
           targets:
           - selectel

   Specify:

   • <selectel_token> — your Selectel token (API key);
   • <keystone_token> — your Keystone token for the project to which you want to transfer the data;
   • <example.com.> — domain name as it appears in DNS hosting (legacy), with a dot at the end. To migrate all domains, instead of the domain name, specify the following "*" without the dot.

4. Start the transfer:

   octodns-sync --config-file=migration_config.yaml --doit

5. In control panel go to DNS → Domain zones.

6. Make sure that you are in the project to which you have moved the data. To do this, open the projects menu (name of the current project) and select the desired project.

7. Ensure that the transferred domains are displayed in the zone list and that each zone's page displays the transferred domain records.

   Resource records of the same type are displayed as a group of records. NS and SOA resource records are not migrated, they will be automatically created in DNS hosting (actual) with default values:

   • NS — a.ns.selectel.ru., b.ns.selectel.ru., c.ns.selectel.ru., d.ns.selectel.ru.
   • SOA IS. a.ns.selectel.ru. support.selectel.ru. <zone_serial_number> 10800 3600 604800 60where <zone_serial_number> — zone serial number, which changes when the zone is updated and signals to the caching servers that records need to be cached again.

   If the data has been migrated incorrectly or incompletely, file a ticket.

Delegate domain to DNS hosting (actual)⁠

If you have transferred multiple domains, you need to delegate each domain.

1. Go to the control panel of the domain registrar where your domain is registered.
2. In the NS records, replace the values with the DNS hosting (actual) NS servers: a.ns.selectel.ru, b.ns.selectel.ru, c.ns.selectel.ru, d.ns.selectel.ru. Specify each server in a separate entry.
3. Wait for the migrated resource records to propagate to the DNS servers. Propagation can take up to 72 hours.
4. Optional: check the records on authoritative servers. Record migration can take up to 72 hours, during which time records will continue to be served from authoritative DNS hosting servers (legacy): ns1.selectel.ru, ns2.selectel.ru, ns3.selectel.ru, ns4.selectel.ru.