Migrating a DNS Service from NetWare to Linux
Being reasonably new to Linux myself I decided to simplify the DNS migration steps supplied by Novell for those administrators embarking on the migration of services from NetWare to Linux. This process was tested migrating the DNS from a Netware 6.5 server to a SLES 9 SP3 server. The process should work in exactly the same way if you're migrating to SLES 10 or OES 1 (Linux).
Install the DNS server
- Start YaST with the command yast.
- Select Software -> Install and Remove Software. Press enter.
- Begin a search in YaST by pressing alt+s.
- Search for the package named bind.
- Select the bind package using the space bar, ensuring that it shows a + next to the package.
- Accept the installation of the package by pressing alt+a.
- YaST will prompt you for your installation CD, and initiate the copy and install process.
Setup the zones on the destination server
- If YaST isn't already open, start it with the command yast.
- Select Network Services -> DNS Server. Press enter.
- Move the cursor six down to DNS zones.
- Tab to zone name field.
- Type in the name of the zone you need to create, select the type, then press alt+a to add the zone.
- The above step needs to be repeated for all the zones which you will be migrating to this server.
- When you have completed adding the zones, press alt+f to finish the setup.
Migrate the zone data
- Each DNS server has a copy of the zone files in SYS:\ETC\DNS. The zone files have the file extension ".db". Be aware of whether your NetWare server is setup as a 'master' / 'primary' or 'slave' / 'secondary'.
- Copy the zone files for the master zones you wish to migrate from your source NetWare server to /var/lib/named/master on your destination server.
- Copy the zone files for the slave zones from your source NetWare server to /var/lib/named/slave on your destination server.
- Remove the .db extension from each file. Assuming the zone is example.com, you can use the command mv example.com.db example.com.
Starting the service
- Start the DNS Server through the command rcnamed start.
- Check that the service has started with the command chkconfig named. The command should display named on.
Starting the service at boot
If you require the service to start at boot time the following commands will ensure that this happens for the correct run levels.
- Connect via SSH
- type "chkconfig -l named", this will return a response similar to "named 0:off 1:off 2:off 3:on 4:off 5:on 6:off". In this case the service will start at boot for runlevels 3 & 5 which is correct for most systems.
- If the above step displayed off for all the runlevels you can add it to the correct runlevels by typing "chkconfig -a named", this will automatically add the service to the correct runlevels. You can verify this step by using "chkconfig -l named" again.
- If however you wish the service not to start at boot you can type "chkconfig -d named" which will remove automatic startup from all runlevels.