In these sections, the supported OES server is referred to as the source server and the OES 2018 SP2 server as the target server.
Make sure your setup addresses the following requirements before you migrate DNS to the new platform.
An eDirectory integrated DNS server installed on the target machine.
NOTE:During DNS installation, do not select Create DNS Server option at the install time. This avoids the creation of the DNS server for the temporary NCP server. So when migration is completed, the existing DNS server objects are considered.
Schema extension is already done on the destination server tree and DNS-DHCP Group, and the RootServerInfo and DNS-DHCP Locator objects are created.
To migrate DNS to the new platform, you can use the Java Management Console. During migration, the configuration details as well as the data are migrated to the destination platform.
Launch Java Console.
Identify the source NCP server and the corresponding DNS server object that should be migrated to target server.
The server and the server object will no longer exist on the OES 2 server after migration. Make sure that the DNS Service is not running on this source NCP server.
To stop the service, see “Stopping the DNS Server” in the OES 2018 SP2: DNS/DHCP Services for Linux Administration Guide.
Use Java Console to move the source DNS server. This task also migrates the primary zones in the tree.
For information about moving the DNS server, see “Moving a DNS Server” in the OES 2018 SP2: DNS/DHCP Services for Linux Administration Guide.
On successful migration, proceed to perform service specific proxy migration, see Migrating Proxy users to OES 2018 SP2.
You can migrate DNS across eDirectory trees by exporting the DNS database from the source server and importing the database to the target server.
Export DNS database operation transfers the resource record data of a zone to a text file. The text file is in the DNS BIND master file format. These files can be used in other DNS servers, including BIND servers, or they can be imported back into the eDirectory database using the DNS/DHCP Java-based Management Console.
In the DNS Service window, select the zone you want to export and click Export DNS Database on the toolbar.
In the Export - DNS window, enter the name of a destination file or browse to select a filename from the dialog box.
Click Export to store your zone data in a file.
If the export program encounters any error, the Details button is enabled. Click Details to view the error details.
Import DNS database operation transfers resource record data present in the BIND formatted DNS zone files into the eDirectory database.
In the DNS Service tab, click Import DNS Database on the toolbar.
Enter the DNS BIND formatted filename in the field provided. You can also browse to select the filename from the File Selection dialog box.
Click Next to select the context where the zone objects will be created.
Click Next to select the server name that manages the zone.
You can select an existing DNS server or an NCP server, where DNS server object will be created. The selected DNS server must have the DNS/DHCP services installed in it.
If you select the zone type as primary, this DNS server will act as a designated primary. If you select the zone type as secondary, this DNS server will act as a designated secondary.If you do not want to assign a DNS server for this zone leave this field empty.
Click Next to specify the zone type.
If you select the zone type as primary, DNS servers act as primary servers for this zone or if you select secondary, servers act as secondary DNS servers.
Click Next to view the configuration that you selected.
Click Import to begin importing with this configuration.
If the import program encounters any error, the Details button is enabled. Click Details to view the error details. Some resource records might not have been transferred because of incorrect data. Click Create on the tool bar to recreate these resource records.
Click Finish to complete the import operation.
Use the Java Management Console to check for the existence of the following objects:
DNS-DHCP
DNSDHCP-GROUP
RootServerInfo
DNS Server object
Load novell-named using the rcnovell-named start command and check to see if the /etc/opt/novell/named/named.conf file contains zone database files with valid information.
Use the nslookup utility to query for records in zones.