Overview of Windows Platform migration to Linux is here.

General Info

  • Migration of DNS hosting from MS DNS to BIND server
  • Migration is possible only for OSA 6.0.6 with HOTFIX 128148 PAU v3 and later.
  • Updating of domains to the new server is performed with the dns_sync.py script

Migration

Preparation

  1. Deploy a new Linux server for BIND according to the Deploying Linux-based DNS Servers section of the Linux Platform Deployment guide.
  2. Install the bind9 service package to the new node.
  3. Download dns_sync.py to the Management Node.
  4. Get IDs of the source MS DNS and destination BIND services (Services > Domains > DNS > Nameservers > ID).

  5. Change the DNS configuration to the BIND server in the activation parameter of the DNS Hosting resource type and all service templates which use this resource type.

    To get the list of resource types and service templates that you need to modify, execute the following script on the Management Node:

    c:\Python27\python.exe dns_sync.py --check --from=MSDNS_ID --to=BIND_IDs

    where:

    MSDNS_ID – service ID of the first MS DNS nameserver,

    BIND_IDs – comma separated IDs of BIND services.

    For example:

    c:\Python27\python.exe dns_sync.py --check --from=3 --to=5,7

Updating of nameservers

  1. Execute the script on MN:

    c:\Python27\python.exe dns_sync.py --sync --from=MSDNS_ID --to=BIND_IDs
  2. Check the script output for failed domains. (detailed logs are stored in the dns_sync.log file)

Post-processing

  1. After all domains were processed, check that MS DNS is not used (Services > Domains > DNS > Nameservers > In Use = No).
  2. Assign MS DNS IP to the BIND server.
  3. Remove the msdns service from the MSDNS node.
  4. Remove the MSDNS node.

Internal content