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 migration was tested on a Netware 6.5 server as well as a SLES 9.3 server. The process should work exactly the same on SLES 10 and OES 1 Linux Service pack 1 & 2.
The original steps for the migration can be found at: http://www.novell.com/documentation/oes/dhcp_enu/index.html?page=/documentation/oes/dhcp_enu/data/btmrx88.html
Phase 1 - yast - select software Ã¢â‚¬Å“It should already be selected as itÃ¢â‚¬â„¢s the first in the list then press tab and down to get to install and remove software press enter - press alt+s - type in bind press enter - press space - ensure + next to bind - press alt+A - make sure cd 1 is in the drive Ã¢â‚¬Å“Obviously this will vary between the different distributions of LinuxÃ¢â‚¬Â - Next the copy process appears - When the copy process has finished tab 3 times - till software is highlighted on the left and move down to network services - tab and down to DNS server press enter - go 6 down to DNS zones - Tab to zone name field. - type in the name of the zone select the type and press alt+a to add the zone - This needs to be repeated for all the zones that need to be migrated. - When you have finished adding all the zones needed press alt+f
This concludes the portion for adding the zones.
Phase 2 - Copy all the zones that were specified as master in phase one from \\Ã¢â‚¬Ânetware serverÃ¢â‚¬Â\sys\etc\dns\Ã¢â‚¬Âzone.dbÃ¢â‚¬Â to /var/lib/named/master on the SLES server. Ensure to remove the .db extension of the zone files. - copy all zones that were specified as slave in phase one from \\Ã¢â‚¬Ânetware serverÃ¢â‚¬Â\sys\etc\dns\Ã¢â‚¬Âzone.dbÃ¢â‚¬Â to /var/lib/named/slave on the SLES server. Ensure that these zones are also renamed as indicated above. note: make sure that the names of the zones created in phase one match the filenames in phase 2 e.g. zone = example.com filename = example.com
Phase 3 Now you can start the service by typing rcnamed start Make sure that it is enabled for startup by typing chkconfig named, it should display Ã¢â‚¬Å“named onÃ¢â‚¬Â If it displays Ã¢â‚¬Å“named offÃ¢â‚¬Â type Ã¢â‚¬Å“chkconfig named 35Ã¢â‚¬Âon this will ensure that the service is started at server boot for runlevels 3 and 5.