In these sections, the NetWare server is referred to as the source server and the OES 2018 server as the target server.
The following sections give you more information on the prerequisites and the procedure to migrate source servers based on different scenarios:
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:In a Server ID Swap scenario, do not selectoption 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.
The user running the migration process should have rights to update files on the target machine. This user should also be included in the DNS-DHCP group in eDirectory.
The following platforms are accepted as valid source platforms for the migration process:
NetWare 6.5 SP8
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.
In this scenario, both the NetWare server and the OES 2018 server are on the same eDirectory tree.
In this scenario, the Netware server and the OES 2018 server are on different eDirectory trees, so the migration is across the trees.
Depending on your setup, you can choose to migrate a single server at a time or migrate all the servers at the same time.
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 NetWare server after migration. Make sure that the DNS Service is not running on this source NCP server.
To stop the service, see OES 2018: 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 OES 2018: DNS/DHCP Services for Linux Administration Guide.
In Java Console, create the DNS server object. For details, see OES 2018: DNS/DHCP Services for Linux Administration Guide.
On the target server, create a secondary zone and specify the zone master IP address as the IP address of the NetWare server where the primary zone exists. After the initial zone transfer, change the zone on the source NetWare server to secondary and make the zone on the target server to be the primary server.
Migrate primary zones on the target server by creating a secondary zone and specifying the zone master IP address as the IP address of the NetWare/OES server where the primary zone exists.
Load the DNS servers on primary and secondary server to initiate zone transfer.
After the initial zone transfer, change the zone on the source NetWare server to secondary and make the zone on the target server to be the primary server zone.
To migrate secondary zones, create a secondary zone on the Linux server and specify it to be the secondary zone to the target primary zone that is on the target server. Ensure that both the primary and the secondary zones use the same name. This is essential for a successful zone transfer.
NOTE:This method of migration is limited to migrating the zone data only.
Use the Java Management Console to check for the existence of the following objects:
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.