Table 17-1 Local and Remote DNS scenarios
|
Case |
Local DNS |
Remote DNS |
|---|---|---|
|
Non-named mapped FRD |
Yes |
No |
|
Non-named mapped child |
Yes |
Yes |
|
Name-mapped FRD |
Yes |
Yes |
|
Name-mapped child domain |
Yes |
Yes |
|
Additional Domain Controller |
Yes |
Yes |
The following items provide more information on DSfW configuration with DNS:
FRD servers are always configured with DNS.
For non-name mapped FRD installation, the locator, group, and rootserverinfo objects are created within the novell container under the domain context. These contexts cannot be edited.
For named mapped FRD, the contexts for locator, group, and rootserverinfo are not populated.
If it is the first DNS server in the tree, then by default these objects are created under the novell container within the domain context.
If it is not the first DNS server in the tree, then the context pointing to the existing locator, group, and rootserver must be entered.
Entering different context results in multiple instances of these objects, which leads to management difficulties.
For child domains, the DNS server can be either local or one of the parent or grandparent DNS servers. For remote DNS servers, the locator and group object contexts are required as inputs.
DNS is not installed for additional domain controllers.
For workstations to join the domain, an Update Policy must be enabled on the zone. Allow-update and update policies are mutually exclusive, so allow-update cannot be used on these zones.
NOTE:While binding to a DSfW server, admin name and context for authentication must be in X500 format and not in the domain name format. The ports should be 1389 for non-secure or 1636 for secure. For example: cn=admin,o=adminusers,dc=acme,dc=com.
Table 17-2 DNS Deployment Scenarios
|
Deployment Scenarios |
Description |
|---|---|
|
Non-name Mapped FRD |
The DSfW service is configured for the new tree. The DNS server is configured on the local server. Because this is a new eDirectory tree being configured for DSfW-DNS, it does not require remote DNS server configuration. |
|
Non-name Mapped Child |
The DNS server is configured locally or configured to point to the remote DNS server (parent DNS server) in the tree. |
|
Name Mapped FRD |
DSfW is configured for an existing eDirectory tree. The DNS server is either configured locally or is configured to point to the remote DNS server in the tree. |
|
Name Mapped Child Domain |
The DNS server is configured for the child domain on the local server or it is configured to point to the remote DNS server (parent DNS server) in the tree. |
|
Additional Domain Controller |
The DNS server is configured locally or is configured to point to the remote DNS server. |