DNS on OES has been integrated with eDirectory. This means you can transition your existing DNS infrastructure from NetWare to OES, as well as centrally administer it the same way you do on NetWare.
To accomplish eDirectory integration for DNS, Novell did a full port of NetWare DNS to OES to make it functionally equivalent to DNS in NetWare 6.5. Novell plans in the future to fully integrate all of the required functionality into the open source BIND project.
Starting with OES, the iManager plug-in is no longer supported for management of DNS on OES. Java Console is the DNS administrative tool. If you are using the Novell NetWare DNS and DHCP services and hosting it via a cluster, this configuration can also be carried forward into an OES environment.
DNS platform differences are summarized in DNS Differences Between NetWare and OES
in the OES 2023: Planning and Implementation Guide.
Table 8-1 DNS Source and Target Server Requirements
|
Source Server |
Target Server |
|---|---|
|
NetWare 5.1 SP8 NetWare 6.0 SP5 or later NetWare 6.5 SP5 or later |
OES or later |
|
The Novell DNS service pattern is installed. |
|
The schema is extended, the DNS-DHCP group is created, and the RootServerInfo and DNS-DHCP Locator objects are created. |
|
The installing administrator has rights to update files on the target server and is a member of the DNS-DHCP Group. |
DNS servers can be transferred both within and across eDirectory trees by using the Java Console. The OES Migration Tool doesn’t support DNS migrations.
For instructions, see Migrating DNS to OES 2023
in the OES 2023: Migration Tool Administration Guide.