Search Engine: Elastic

Article ID: 4016, created on Mar 18, 2008, last review on Jul 14, 2018

  • Applies to:
  • Odin Automation
  • Odin Business Automation Standard 4.5


Please use the following steps to perform such an operation:

  1. Assign a new IP-address to the old nameserver or set up a new nameserver.

  2. Make sure that the nameserver is accessible via the new IP-address.

  3. Update DNS records for the nameserver in the Odin Business Automation Standard system: Top > Service Director > Domain Manager > Domains > Nameserver domain > DNS zone tab.

  4. Update DNS records for the nameserver on the DNS registrar if it is required.

  5. Save a copy of the named configuration file:

        a. Go to Top > Service Director > Domain Manager > Name Servers > Nameserver and copy the absolute path to the configuration file specified in the “Path to the named configuration file on the remote server.” 

        b. Log in on the old nameserver and copy the existing configuration file.

  6. Update the IP of the nameserver:

        a. Go to Top > Service Director > Domain Manager > Name Servers > Nameserver and click on the “Edit” button.

        b. Change the IP address; switch SSH install mode to Use the root password; enter the root password for the new nameserver; change the path to the configuration file if required; and click on the save button.

  7. Check that the new nameserver works correctly:

        a. Log in to the new nameserver.

        b. Execute the /etc/init.d/named restart command.

        c. Make sure that the service was started without errors.

    If the named service fails to start because of errors in the configuration file:     d. Replace its content with the content of the old configuration file saved in step 5;

        e. Replace all occurrences of the old IP with the new one;

        f.  Repeat points b. and c.     

  8. Release the old IP address from the nameserver or stop the old nameserver.

Additional Information

To change the IP address of the Container-manageable nameserver, please check the following article:

400e18f6ede9f8be5575a475d2d6b0a6 8fc71f07abe5b233fea1ae0377cd5e3d 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF