Skip to main content
Transfer domains from DNS hosting (legacy) to DNS hosting

Transfer domains from DNS hosting (legacy) to DNS hosting

warning

We've released new version of DNS hosting and we're gradually shutting down legacy according to stages.

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

If you registered after January 30, 2024, you are only available to DNS hosting.

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) only has 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 one project.

You can transfer domains:

Once you have migrated to DNS hosting 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.

Transfer data⁠

  1. В control panels go to Network services → DNS hosting.

  2. Click Copying zones to DNSv2.

  3. Select project where the zones need to be moved to.

  4. Click Copy. When the window closes, the transfer is complete.

  5. To check the result of the transfer, go to the section DNS → Domain zones.

  6. Make sure you are in the project to which you migrated the data.

  7. 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.srv.cr., b.ns.srv.cr., c.ns.srv.cr., d.ns.srv.cr.
    • SOA IS. a.ns.srv.cr. dns.cloudflare.com. <zone_serial_number> 10000 2400 604800 1800where <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⁠

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 NS servers: a.ns.srv.cr, b.ns.srv.cr, c.ns.srv.cr, d.ns.srv.cr. 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.servercore.com, ns2.servercore.com, ns3.servercore.com, ns4.servercore.com.

Transfer domain via octoDNS⁠

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

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 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 Servercore provider for octoDNS:

    pip3 install octodns_servercore

  9. 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 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:
      servercore_legacy:
        class: octodns_servercore.ServercoreProviderLegacy
        token: <servercore_token>
      servercore:
        class: octodns_servercore.ServercoreProvider
        token: <keystone_token>

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

    Specify:

    • <servercore_token> — your Servercore 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 "*" without the dot.

  4. Start the transfer:

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

  5. В control panels 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. 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.srv.cr., b.ns.srv.cr., c.ns.srv.cr., d.ns.srv.cr.
    • SOA IS. a.ns.srv.cr. dns.cloudflare.com. <zone_serial_number> 10000 2400 604800 1800where <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⁠

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 NS servers: a.ns.srv.cr, b.ns.srv.cr, c.ns.srv.cr, d.ns.srv.cr. 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.servercore.com, ns2.servercore.com, ns3.servercore.com, ns4.servercore.com.