Setting Up A Windows Dns Server For Dsfw; Migrating Dns To Another Domain Controller - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual

13.3 Setting Up a Windows DNS Server for DSfW

Although it is possible to migrate DSfW DNS to a Windows DNS server, the migrated DNS records
cannot be integrated with Active Directory. Use the following procedure to migrate DSfW DNS
server to a Windows DNS server.
1 Using MMC, add secondary zones for all the existing forward and reverse lookup zones hosted
in the DSfW DNS server.
Windows DNS does a zone transfer of the newly created zones from the DSfW server.
2 Using iManager or the DNS/DHCP Management Console, configure the servers that were
designated as primary servers to be secondary servers.
3 In the first domain controller, edit the
the server where the Windows DNS Server is running
4 Restart Novell DNS server for the changes to take effect by using the
restart
13.4 Migrating DNS to Another Domain
Controller
In a typical DSfW deployment, the DNS server exists on the first domain controller of the domain.
Any subsequent domain controller in the domain, cannot be configured as a DNS server. So, all the
subsequent domain controllers in the domain, use the DNS server that is being used by the first
domain controller.
If the first domain controller of the domain does not function due to a hardware or software fault, the
other domain controllers need at least one DNS server to keep the domain services intact.
IMPORTANT: The DNS migration can happen even when the source DNS server is down. If the
DNS server is down, make sure that any of the subsequent domain controllers in the forest have the
replica of the Tree Root partition. This is necessary to perform
When the first domain controller goes down, make sure that the configuration partition and schema
partition replica is there on at least one domain controller in the domain. This is required to keep the
functioning of DSfW intact.
To migrate the DNS server from the first domain controller, from the subsequent domain controller
execute the following steps:
1 Using the
controller with the following commands.
KEYVALUE=<dns-admin_dn> CASA-cli -s -n dns-ldap -k CN
KEYVALUE=<password> CASA-cli -s -n dns-ldap -k Password
TIP: The
steps, install the
2 Using iManager, execute the following steps:
2a Click DNS>DNS Server Management>Create Server option.
144 OES 2 SP2: Domain Services for Windows Administration Guide
command.
client utility, set the CASA credentials on the subsequent domain
CASA-cli
client utility is not installed by default with OES2 SP2. To execute these
CASA-cli
package using YaST.
CASA-cli
file and change the IP address to
/etc/resolv.conf
Step 2.
rc-novell-named