Environment
Novell NetWare 6.5
Novell Open Enterprise Server 2 (OES 2) Linux
Novell DNS
Novell DNS Management Console
Situation
While there is a migration utility provided to migrate DNS from NetWare to OES 2, whether or not the DNS servers are in the same tree, there are a couple of options to simplify this process without the migration wizard. This doesn't eliminate every need for the migration wizard, but will simplify the process for many administrators.
Resolution
The steps can be completed via iManager or the DNS/DHCP Java Management console; however, the steps listed below are specific to only the Management Console. The steps to do accomplish the same steps in iManager should be pretty straight forward by understanding what is being done in the content below.
OPTION 1 (NetWare and OES Servers part of same tree):
Open the DNS/DHCP Management Console and click on the DNS tab at the top.
- Make sure that the new OES 2 server in the tree has DNS configured on it, and that a DNS server object has been created
- If the object is missing, run the 'yast2 oes-install' tool, install DNS, and configure it
- Highlight the DNS zone that needs to be transferred to the OES 2 server (from NetWare)
- If step 2 has been completed, the "Available DNS Servers" list should contain the OES 2 DNS server object
- Highlight the OES 2 DNS server under the same section, and click the "Add" button to add it to the "Authoritative DNS Servers" list
- Change the "Designated Primary" (or secondary if this is a secondary zone) to the OES 2 server
- All done! No migration wizard needed! Restart the named service
- NOTE: If removing NetWare from the tree, remove the NetWare DNS Server from the "Authoritative DNS Servers" list
- This works for forward and reverse zones
- If a "transfer ID" or consolidation option is needed, then the migration wizard will be needed
OPTION 2 (NetWare and OES NOT in same tree):
- NOTE: This should theoretically work for transferring other DNS Zones from other Operating Systems (Microsoft, SLES, and others) as long as zone transfers are allowed
- Make sure that the new OES 2 server in the tree has DNS configured on it, and that a DNS server object has been created
- If the object is missing, run the 'yast2 oes-install' tool, install DNS, and configure it
- Create a secondary zone and point to the IP address of the DNS server where prompted
- Restart DNS on the OES server and give the zone some time to transfer the information
- Once the zone data has been transferred, change the zone type from secondary to primary
- All done! Restart the named service