Skip to main content
Transfer domains from DNS hosting (legacy) to DNS hosting (actual)
Last update:

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

For your information

We have released [a new version of DNS hosting (actual)](https://my.selectel.ru/dns /) and stop supporting and developing legacy version. Domains and resource records in DNS hosting (legacy) continue to work, we will warn you in advance about the termination of their work.

We recommend transferring domains and resource records to DNS hosting (actual) now to avoid disruption of sites when DNS hosting is disabled (legacy).

Domain transfer takes place without pauses in DNS operation. You create a copy of the data from DNS hosting (legacy) in DNS hosting (actual), and then delegate record management to authoritative DNS hosting servers (actual). The transfer can take up to 72 hours, during which time records will continue to be sent from reputable DNS hosting servers (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 one project.

You can transfer domains:

After transferring to DNS hosting (actual), you can transfer the domain zone between projects.

Transfer domain via control panel

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

1. Transfer data

  1. In the [control panel](https://my.selectel.ru/dns /) go to DNSDomain Zones.

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

  3. Go to the section Network servicesDNS hosting.

  4. Click Copy Zones.

  5. Paste the recipient project ID and click Copy. When the window closes, the copying will be completed.

  6. In the [control panel](https://my.selectel.ru/dns /) go to DNSDomain Zones.

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

  8. Make sure that the migrated domains are displayed in the list of zones, and the migrated domain records are displayed on the page of each zone.

    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 — a.ns.selectel.ru . support.selectel.ru . <zone_serial_number> 10800 3600 604800 60, where <zone_serial_number> is the serial number of the zone, which 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 not completely, create a ticket.

2. Delegate the domain to DNS hosting (actual)

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

  1. Go to the control panel of the domain registrar where your domain is registered.
  2. In NS records, replace the values with NS DNS hosting servers (actual): 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 until the migrated resource records are distributed to the DNS servers. Distribution can take up to 72 hours.
  4. Optional: check records on reputable servers. Transferring records can take up to 72 hours, during which time records will continue to be sent from reputable 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 data.
  3. Delegate domain to DNS hosting (actual).

1. Install OctoDNS

  1. Install Python 3, virtualenv and pip3:

    sudo apt-get update
    sudo apt-get install python3 virtualenv
    sudo apt-get install python3-pip
  2. Create a directory to work with OctoDNS:

    mkdir ~/octodns
  3. Go to the '~/octodns` directory:

    cd ~/octodns
  4. Create a virtual environment for working 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 is installed correctly:

    octodns-sync --version

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

    octoDNS 1.4.0
  8. Install Selectel provider for OctoDNS:

    pip3 install octodns_selectel
  9. Check that the Selectel provider is installed correctly:

    pip3 list | grep octodns-selectel

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

    octodns_selectel 0.99.1

    The minimum version of the Selectel provider to transfer is `0.99.1'.

2. Transfer data

  1. Go to the ~/octodns directory:

    cd ~/octodns
  2. Create the file migration_config.yaml:

    nano migration_config.yaml
  3. Copy the contents to 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 .> is the domain name in the form in which it is specified in DNS hosting (legacy), with a dot at the end. To transfer all domains, specify "*" without a dot instead of the domain name.
  4. Start the transfer:

    octodns-sync --config-file=migration_config.yaml --doit
  5. In the [control panel](https://my.selectel.ru/dns /) go to DNSDomain Zones.

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

  7. Make sure that the migrated domains are displayed in the list of zones, and the migrated domain records are displayed on the page of each zone.

    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 — a.ns.selectel.ru . support.selectel.ru . <zone_serial_number> 10800 3600 604800 60, where <zone_serial_number> is the serial number of the zone, which 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 not completely, create a ticket.

3. Delegate the domain to DNS hosting (actual)

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

  1. Go to the control panel of the domain registrar where your domain is registered.
  2. In NS records, replace the values with NS DNS hosting servers (actual): 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 until the migrated resource records are distributed to the DNS servers. Distribution can take up to 72 hours.
  4. Optional: check records on reputable servers. Transferring records can take up to 72 hours, during which time records will continue to be sent from reputable DNS hosting servers (legacy): ns1.selectel.ru , ns2.selectel.ru , ns3.selectel.ru , ns4.selectel.ru .