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

warning

We have released a new version of DNS hosting (actual) and are gradually disabling the legacy version according to the steps.

Transfer domains to DNS hosting (actual) now to avoid disruption of sites when DNS hosting (legacy) goes down.

If you registered after January 30, 2024, only DNS hosting (actual) is available to you.

Domain transfers happen without pausing DNS operations. You create a copy of the data from DNS hosting (legacy) in DNS hosting, and then delegate record management to the authoritative servers in DNS hosting. 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) has only NS and SOA records, it will not be migrated to DNS hosting. 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 a single project.

You can transfer domains:

After the transfer to DNS hosting, you can transfer the domain zone to another project.

Transfer a domain through the control panel⁠

1. Transfer data⁠

In the control panel, click Products in the top menu and select Legacy DNS hosting.
Click Copy Zones to DNSv2.
Select the project to which you want to transfer zones.
Click Copy. When the window closes, the transfer is complete.
To check the result of the migration, click Products in the top menu and select DNS hosting.
Make sure you are in the project to which you migrated the data.
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 with default values:
- NS — a.ns.servercore. ru., b.ns.srv.cr., c.ns.srv.cr., d.ns. servercore``.ru.
- SOA — a.ns.srv.cr. dns.cloudflare.com. <zone_serial_number> 10000 2400 604800 1800, where <zone_serial_number> is the zone serial number, which changes when the zone is updated and signals the caching servers that records need to be cached again.
If the data was migrated incorrectly or incompletely, create a ticket.

2. Delegate domain to DNS hosting⁠

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

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

Transfer domain via octoDNS⁠

1. Install octoDNS⁠

Install Python 3, virtualenv, and pip3:

Linux
macOS

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

brew install python3
brew install virtualenv

Create a directory to work with octoDNS:
```
mkdir ~/octodns
```
Navigate to the ~/octodns directory:
```
cd ~/octodns
```
Create a virtual environment to work with octoDNS:
```
virtualenv env
```
Activate the virtual environment:
```
source env/bin/activate
```
Install octoDNS in a virtual environment:
```
pip3 install octodns
```
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
```
Set the Servercore provider for octoDNS:
```
pip3 install octodns_servercore
```
Check that the Servercore provider has been installed correctly:
```
pip3 list | grep octodns-servercore
```
The response will show the installed version of the ISP, for example:
```
octodns_servercore 0.99.1
```
The minimum Servercore provider version to migrate is 0.99.1.

2. Transfer data⁠

Navigate to the ~/octodns directory:
```
cd ~/octodns
```
Create the migration_config.yaml file:
```
nano migration_config.yaml
```

Copy the contents into the file:

---
processors:
  no-root-ns:
    class: octodns.processor.filter.IgnoreRootNsFilter

providers:
  servercore_legacy:
    class: octodns_servercore.ServercoreProviderLegacy
    token: <x_token>
  servercore:
    class: octodns_servercore.ServercoreProvider
    token: <x_auth_token>

zones:
    <example.com.>:
        sources:
        - servercore_legacy
        processors:
        - no-root-ns
        targets:
        - servercore

Specify:

<x_token> — static token (X-Token);
<x_auth_token> — IAM token for the project to which you need to transfer 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 a "*" without the period.

Start the transfer:

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

In the control panel, in the top menu, click Products and select DNS hosting.
Make sure you are in the project to which you migrated the data.
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 with default values:
- NS — a.ns.servercore. ru., b.ns.srv.cr., c.ns.srv.cr., d.ns. servercore``.ru.
- SOA — a.ns.srv.cr. dns.cloudflare.com. <zone_serial_number> 10000 2400 604800 1800, where <zone_serial_number> is the zone serial number, which changes when the zone is updated and signals the caching servers that records need to be cached again.
If the data was migrated incorrectly or incompletely, create a ticket.

3. Delegate domain to DNS hosting⁠

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

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

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

Transfer a domain through the control panel⁠​

1. Transfer data⁠​

2. Delegate domain to DNS hosting⁠​

Transfer domain via octoDNS⁠​

1. Install octoDNS⁠​

2. Transfer data⁠​

3. Delegate domain to DNS hosting⁠​