Migrate domains from DNS hosting (legacy) to Selectel DNS hosting (actual)
We have released a new version of DNS hosting (actual) and are gradually phasing out the legacy version (legacy) according to the stages.
Transfer domains to DNS hosting (actual) now to avoid website disruptions when DNS hosting (legacy) is phased out.
If you signed up after January 30, 2024, only DNS hosting (actual) is available to you.
Domain migration occurs without DNS downtime. You create a copy of the data from DNS hosting (legacy) in DNS hosting (actual) and then delegate record management to the authoritative servers of DNS hosting (actual). The migration may take up to 72 hours; during this time, records will continue to be served by the authoritative servers of DNS hosting (legacy).
If a domain in DNS hosting (legacy) has only NS and SOA records, it will not be transferred to DNS hosting (actual). If you need to transfer such a domain, you need to add it via the control panel.
All domains from DNS hosting (legacy) are transferred to a single project.
You can migrate domains:
After transferring to DNS hosting (actual), you can transfer the domain zone to another project.
Migrate domains via the control panel
1. Migrate data
-
In the control panel, in the top menu, click Products and select DNS hosting Legacy.
-
Click Copy zones to DNSv2.
-
Select the project to which you want to transfer the zones.
-
Click Copy. When the window closes, the transfer will be completed.
-
To check the transfer result, click Products in the top menu and select DNS hosting.
-
Ensure you are in the project to which you migrated the data.
-
Check that the migrated domains appear in the zones list, and that the migrated domain records appear on each zone's page.
Resource records of one 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 that cannot be edited:
- NS —
a.ns.selectel.ru.,b.ns.selectel.ru.,c.ns.selectel.ru.,d.ns.selectel.ru. - SOA —
a.ns.selectel.ru. support.selectel.ru.<zone_serial_number> 10800 3600 604800 60, where<zone_serial_number>is the zone serial number that changes when the zone is updated and signals caching servers that the records need to be cached again.
If the data was transferred incorrectly or incompletely, submit a ticket.
- NS —
2. Delegate domain to DNS hosting (actual)
If you migrated multiple domains, you must delegate each one.
- Go to the control panel of the domain registrar where your domain is registered.
- 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 record. - Wait for the transferred resource records to propagate to the DNS servers. Record propagation can take up to 72 hours, during which records will continue to be served from authoritative servers of DNS hosting (legacy):
ns1.selectel.ru,ns2.selectel.ru,ns3.selectel.ru,ns4.selectel.ru. - Optional: check records on authoritative servers.
Migrate domains via octoDNS
1. Install octoDNS
-
Install Python 3, virtualenv, and pip3:
Linux
macOS
sudo apt-get updatesudo apt-get install python3 virtualenvsudo apt-get install python3-pip -
Create a directory for octoDNS:
mkdir ~/octodns -
Go to the
~/octodnsdirectory:cd ~/octodns -
Create a virtual environment for octoDNS:
virtualenv env -
Activate the virtual environment:
source env/bin/activate -
Install octoDNS in the virtual environment:
pip3 install octodns -
Check that the package was installed correctly:
octodns-sync --versionThe response will show the installed octoDNS version, for example:
octoDNS 1.4.0 -
Install the Selectel provider for octoDNS:
pip3 install octodns_selectel -
Check that the Selectel provider was installed correctly:
pip3 list | grep octodns-selectelThe response will show the installed provider version, for example:
octodns_selectel 0.99.1The minimum version of the Selectel provider for migration is
0.99.1.
2. Migrate data
-
Go to the
~/octodnsdirectory:cd ~/octodns -
Create a
migration_config.yamlfile:nano migration_config.yaml -
Copy the contents into the file:
---processors:no-root-ns:class: octodns.processor.filter.IgnoreRootNsFilterproviders:selectel_legacy:class: octodns_selectel.SelectelProviderLegacytoken: <x_token>selectel:class: octodns_selectel.SelectelProvidertoken: <x_auth_token>zones:<example.com.>:sources:- selectel_legacyprocessors:- no-root-nstargets:- selectelSpecify:
<x_token>— static token (X-Token);<x_auth_token>— IAM token for the project to which you want to transfer the data;<example.com.>— domain name in the form specified in DNS hosting (legacy), with a trailing dot. To transfer all domains, specify"*"without a dot instead of the domain name.
-
Start the migration:
octodns-sync --config-file=migration_config.yaml --doit -
In the control panel, in the top menu, click Products and select DNS hosting.
-
Ensure you are in the project to which you migrated the data.
-
Check that the migrated domains appear in the zones list, and that the migrated domain records appear on each zone's page.
Resource records of one 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 —
a.ns.selectel.ru. support.selectel.ru.<zone_serial_number> 10800 3600 604800 60, where<zone_serial_number>is the zone serial number that changes when the zone is updated and signals caching servers that the records need to be cached again.
If the data was transferred incorrectly or incompletely, submit a ticket.
- NS —
3. Delegate domain to DNS hosting (actual)
If you migrated multiple domains, you must delegate each one.
- Go to the control panel of the domain registrar where your domain is registered.
- 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 record. - Wait for the transferred resource records to propagate to the DNS servers. Record propagation can take up to 72 hours, during which records will continue to be served from authoritative servers of DNS hosting (legacy):
ns1.selectel.ru,ns2.selectel.ru,ns3.selectel.ru,ns4.selectel.ru. - Optional: check records on authoritative servers.