Configuring the scope settings for a session significantly improves the session's performance. If you do not configure the scope settings for the session, you receive a warning before every task you attempt to perform. However, you can still proceed with the task.
Setting the scope of the DNS services requires two specifications for the session: the Novell eDirectory context of the Locator object and the administrative scope of the session. Specifying the eDirectory context of the Locator object at the start of the session significantly improves performance because it eliminates the need to search for the Locator object. Specifying the administrative scope of the session also improves performance significantly because it restricts the retrieval of DNS objects for viewing to the scope you specify.
When you configure the DNS scope settings for a session, they only last as long as the session lasts. If you start a new session, you must configure the DNS scope settings again.
To configure DNS scope settings:
Click
> to open the DNS Scope Settings window.Specify the eDirectory context of the DNS Locator object or browse to select it.
Specify the eDirectory context of the container object that will provide the administrative scope of the current session.
If you specify only the eDirectory context of the DNS Locator object and not the administrative scope of the current session, you can proceed with administrative tasks without receiving a warning message. However, performance is further optimized if you also define the administrative scope.
Click
A message indicates that the scope setting request was successful.
Click
to complete the process.Or
Click
to configure the scope settings again.The DNS Server Management role consists of the following tasks:
Use iManager to create and set up a server object for each DNS server you plan to operate.
In iManager, click
to open the DNS Server Management window in the main panel.From the drop-down menu, select
and click to open the Create DNS Server window.Type the NCP server name or browse to select an NCP server from the eDirectory tree.
Specify a unique hostname for the DNS server object.
Specify a domain name for the server object.
Click
.A message indicates that the new DNS server was created.
NOTE:To configure DNS for an existing NetWare 6.5 server, create the DNS server to use the iManager plug-in for DNS. If server is created, then NetWare 6.5 NCP Server should have a DNIP:LocaterPtr attribute pointing to the DNS Locator object.
After you create a DNS server object, you can modify its configuration parameters.
In iManager, click
to open the DNS Server Management window in the main panel.From the drop-down menu, select
and click to open the View/Modify Server window.Select the DNS server from the drop-down list, then click
.Follow the on-screen instructions to view and modify the following DNS server configuration parameters:
List of Zones: The names of the zones that the server manages along with the roles of this server for each of the zones. This field cannot be edited.
DNS Server IP Address: The IP addresses on which the DNS server listens for queries. This field cannot be edited.
DNS TSIG Key Information: Information on available and associated keys.
Available DNS TSIG Keys: A list of DNS TSIG keys that are available in the eDirectory tree. These keys can be associated with the DNS server.
Associated DNS TSIG Keys: A list of DNS TSIG keys that are associated with the DNS server.
Domain name: The domain name of the DNS server.
Comments: Add your comments about the DNS server. This parameter is optional.
Forward List: A list of IP addresses of DNS servers to which unresolved queries will be forwarded.
You can also use this list to control the behavior of queries for which the server is not authoritative and the answers do not exist in the cache. Values can be either First or Only. If you specify the value as First, which is the default, the server queries the list of forwarders first. If no answer is found, the server searches for the answer. If you specify the value as Only, the server queries only the forwarders list.
No-Forward List: A list of domain names whose unresolved queries will not be forwarded to other DNS servers.
Allow Recursion: A list of IP addresses or networks that can submit recursive DNS queries. If you want to disable recursion, specify a value of None.
Query Filter: A list of IP addresses or networks that are authorized to query the DNS server. If no IP address is specified, queries are allowed from all hosts.
Zone Out Filter: A list of IP addresses or networks that are authorized to perform zone transfer from the DNS server.
Also Notify: A list of IP addresses of name servers that receive Notify messages, when a fresh copy of the zone is loaded.
Blacklist Server: Specifies a list of IP addresses of servers that are not approved. The DNS server does not answer queries from or forward queries to the servers listed.
Maximum Cache Size: The maximum amount of memory in kilobytes that the server can use as cache.
Maximum Recursion Lookups: The maximum number of simultaneous recursive lookups the server performs on behalf of the clients.
Current Set of Additional Options: The additional global server and zone options. To view the options, click
to open the View/Modify Server window.Check Names: Restrictions on the character set and syntax of certain domain names in the master zone and the DNS response received from the network.For masters, slave zones, and network responses, the default is to ignore them. This parameter applies to the owner names of A, AAA, and MX records. It also applies to domain names in the RDATA of NS, SOA, and MX records, and to the RDATA of PTR records where the owner name indicates that it is a reverse lookup of a hostname.
Click
to open the DNS Server Management window in the main panel.From the drop-down menu, select
and click to open the Delete DNS Server window.To remove all DNS servers in the list, click the top-level check box and click
or
To remove one or more DNS servers, click the check box next to it and click
.In iManager, click
to open the DNS Server Management window in the main panel.From the drop-down menu, select
Server and click to open the Load/Unload DNS server window.Select the DNS server and specify the port number on which the DNS server is configured.
This port is required to check whether the DNS server is running or not. By default, port 53 is used if no other port number is specified.
Click
.Depending on the state and the version of the DNS server, one of the following happens:
If novell-named is not loaded on the machine, you are prompted to load novell-named.
If novell-named is already loaded on the machine, you are prompted to unload it. To unload novell-named, click
.Currently, it is not possible to load novell-named using command line options from DNS iManager on Linux.
Click
to complete the task.This task enables you to move DNS Services from one NCP server to another NCP server. You can also convert a DNS server into a cluster-enabled DNS server by moving it to a virtual NCP server.
In iManager, click
to open the DNS Server Management window in the main panel.From the drop-down menu, select
r and click to open the Move DNS Server window.Select the DNS server name from the drop-down list.Only OES 2 Linux servers are displayed in this list.
Specify the name of the NCP Server that the DNS Services will be moved to, or use the Object Selector icon to browse and select it.
Click
.The DNS Zone object is an eDirectory container object that is made up of Resource Record Set (RRSet) objects and resource records.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the Create DNS Zone window.Select
.Specify the eDirectory context for the zone or browse to select it.
Specify a name for the zone.
Select
as the Zone Type.Select a DNS server from the
drop-down menu.or
Specify a unique hostname in the
box and select a domain by clicking the button, then click .Click
.A message indicates that the new primary zone has been created.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
, then click to open the Create DNS Zone window.Select
.Specify the eDirectory context for the zone or browse to select it.
Specify a name for the zone.
Select Forward as the
.Select a DNS server from the
drop-down menu. This parameter is optional.or
Specify a unique hostname in the
box and select a domain by clicking the button, then click .Click
.A message indicates that the new forward zone has been created.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
, then click to open the Create DNS Zone window.Select
.Specify the eDirectory context for the zone or browse to select it.
Specify a name for the zone.
Select
as the .Specify the IP address of the DNS server that will provide zone out transfers for this secondary zone.
Select a DNS server from the
drop-down menu. This parameter is optional.or
Specify a unique hostname in the
box and select a domain by clicking the button, then click .Click
.A message indicates that the new secondary zone has been created.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the Create DNS Zone window.Select
.Specify the eDirectory context for the zone or browse to select it.
Specify the network address of the zone in the
field.For example, specify 143.72.155 for 155.72.143.IN-ADDR.ARPA.
The IN-ADDR.ARPA zone name is displayed in the
field.Select the
as Primary (default).Select a DNS server from the
drop-down menu. This parameter is optional.or
Specify a unique hostname in the
box and select a domain by clicking the button, then click .Click
.A message indicates that the new Primary IN-AD DR.ARPA Zone object has been created.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
, then click to open the Create DNS Zone window.Select
.Specify the eDirectory context for the zone or browse to select it.
Specify the network address in the
field.The IN-ADDR.ARPA zone name is displayed in the
field.Select the
, then select .Select a DNS server from the
drop-down menu. This parameter is optional.or
Specify a unique hostname in the
box and select a domain by clicking the button, then click .Click
.A message indicates that the new Forward IN-ADDR.ARPA Zone object has been created.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
, then click to open the Create DNS Zone window.Select Create
.Specify the eDirectory context for the zone or browse to select it.
Specify the network address in the
field.The IN-ADDR.ARPA zone name is displayed in the
field.Under the
, select .Select a DNS server from the
drop-down menu.or
Specify a unique hostname in the
box and, optionally, specify a domain name or select it from the drop-down menu.Specify the IP address of the DNS server that will provide zone-out transfers for this secondary zone.
Click
.A message indicates that the new Secondary IN-ADDR.ARPA Zone object has been created.
After you have created a Zone object, you can modify it and provide more detailed configuration information.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the View/Modify Zone window.Select the DNS Zone object from the drop-down menu.
Click
.Modify the following DNS Zone configuration parameters.
Zone Type: Specifies whether the zone is a primary or secondary zone.
To configure a server as a passive primary for a zone, specify the server name in the
field of that zone. Make sure this server name is not in the field.To configure a server as designated primary DNS server, specify the server name in the
field of that zone and select that server name from the field.To configure a server as a passive secondary for a zone, specify the server name in the
field of that zone. Make sure this server name is not in the field.To configure a server as designated secondary server, specify the server name in the Authoritative DNS servers field and select that server name in the
field.NOTE:It is not possible to change the zone type from primary/secondary to forward and vice versa.
Zone Master IP Address: If the zone type is secondary, specify the IP address of the master server for this zone.
Available DNS Servers: Lists the available DNS Servers that are not assigned to this zone.
Authoritative DNS Servers: Lists all authoritative servers for this zone.
Click
to assign all available DNS servers to a zone.Click
to remove all authoritative DNS servers from a zone.Designated DNS Server: The DNS server selected in this field will act as a designated primary or designated secondary server depending on whether the zone type is primary or secondary.
Comments: You can provide information about the zone in this field. This parameter is optional.
Forward List: Specifies a list of DNS servers to which unresolved queries are sent.
Forwarder: Controls the behavior of queries for which the server is not authoritative and the answers do not exist in the cache. Values can be either First or Only. The default is First. If you specify the value as First, the server will query the forwarders list first and, if the answer is not found, the server will search for the answer. If you specify the value as Only, the server will query only the forwarders list.
Modify Zone Out Filter: Specifies a list of IP addresses or networks authorized to perform zone transfers for this zone from the DNS server managing it.
Zone Master: Specifies the domain name of the master DNS server.
E-mail Address: Specifies the e-mail address (with @ replaced by a dot) of the person responsible for this zone.
Serial Number: Use this field to set a version number for the Start of Authority.
Interval values: Select from the following values:
Refresh: Specifies the time interval before the secondary name server transfers a copy of the zone data to the primary name server. The default is 180 minutes.
Retry: Specifies the time that a secondary name server waits after a transfer has failed and before it tries to download the zone database again. The default is 60 minutes.
Expire: Specifies the time after which a secondary name server will be unable to download a zone database. The default is 168 hours.
Minimal TTL: Specifies the minimum TTL for a resource record. This parameter determines the period for which a DNS server retains an address mapping in the cache. The default is 24 hours.
Select the
check box, then click to modify the following values:Query Filter: Specifies a list of IP addresses or networks that are authorized to query the DNS server for this zone. This list overrides the query filter specified at the server for this zone.
To add the IP address:
Click
Specify the IP address and the mask length.
The network number is optional.
If you want to add a generic option, check the Predefined match-list to select from the available options in the drop-down list.
Check the Key option and specify the DNS key from the drop-down list.
Click OK.
To delete the IP address, select the item to be deleted, then click .
Also Notify: Specifies a list of IP addresses of name servers that receive Notify messages, when a fresh copy of the zone is loaded.
To add the IP address, Click , specify the IP address, then click OK.
To delete the IP address, select the IP address you want to delete, then click .
Allow Update: Specifies a list of IP addresses or network addresses that are authorized to send updates for this zone. If this option is not configured, the default value of none is used, where no host is authorized to send updates.
To add the address match list element:
Click
Specify the IP address and the mask length.
The network number is optional.
If you want to add a generic option, check the Predefined match-list to select from the available options in the drop-down list.
Select the TSIG key option from the drop-down list. If not specified, then the default value is none.
Click OK.
To delete the address match list element, select the item to be deleted, then click .
Update Policy: Specifies the policy to update the measure to implement security for a zone object. This is implemented by the default DNS server administering the zone. The update policy is a five-token string where each token has a definite function to perform. The syntax for update policy is: Permission Identity MatchType TName RR
To add the update policy:
Click
Select the Permission from the drop-down list. The permission can either be a grant or a deny.
Specify the Identity that refers to the name of the key used to sign the update.
Specify the MatchType from the drop-down list.
name: Matches when the domain name being updated is the same as the name in the name field.
subdomain: Matches when the domain name being updated is a subdomain of (that is, ends in) the name in the name field. The domain name must still be in the zone.
wildcard: Matches when the domain name being updated matches the wildcard expression in the name field.
self: Matches when the domain name being updated is the same as the name in the identity field, not the name field that is when the domain name being updated is the same as the name of the key used to sign the update. If nametype is self, then the name field is ignored; however, you should include the name field when using a nametype of self.
: Specify the which is the domain name appropriate to the specified.
(Optional): Specify the
(Resource Record), which can contain any valid record type.NOTE:The Allow Update with keys option and the Update Policy options are supported for Linux DNS only.
Click Next to associate the DNS TSIG keys with the Zone.
NOTE:In earlier versions, key association was a must before updating a policy. Now, it is not required for SAM because the keys are negotiated at run time. Because of this, no checking is done to validate the identity field for SAM-based updates.
Available DNS TSIG Keys: Displays a list of DNS TSIG keys that are available in the eDirectory tree. These keys can be associated with the Zone.
Associated DNS TSIG Keys: Displays a list of DNS TSIG Keys that are associated with the Zone.
To add the DNS TSIG Key, then select the key > click
.To remove the DNS TSIG key, then select the key > click
.To add all the keys, click
.To remove all the keys, click
.NOTE:To add or remove multiple keys, use the Ctrl key to select the keys, then click
or .Click
to specify the current set of additional options. To modify the options, click . Select the appropriate option from the list. The following are the additional options for the zone:allow-notify: Specifies the list of hosts that are allowed to notify the slaves of zone changes in addition to the zone masters. You can configure this option only for a secondary zone.
To add the address list:
Click Add.
Specify the IP address and the mask length. The mask length is optional. OR Check Predefined match-list to select from the available options from the drop-down list. If you select None, the server will reject notifies sent by any other server.
Click OK.
To delete the address list:
Select the IP address to be deleted.
Click Remove.
Allow-notify specified at the server level is overridden by the settings of this zone.
max-journal-size: Sets a maximum size in bytes for the journal file. This should be configured only for a Linux zone.
NOTE:All changes made to a zone by using dynamic update are written to the zone's journal file. The server periodically flushes the complete contents of the updated zone to its zone file. This happens approximately every 15 minutes. When a server is restarted after a shutdown, it replays the journal file to incorporate into the zone any updates that took place after the last zone file update.The dynamic reconfig interval setting is immaterial for a max-journal-size event triggering.
notify: Specifies if the notification of any zone data changes has to be sent to a slave server. You can select from the following options:
Yes: A notification is sent to all the name servers of the zone when the zone data changes.
Explicit: A notification is sent explicitly to the servers specified in the also-notify list when the zone data changes.
No: A notification is not sent.
A notification specified at the server level is overridden by the settings of this zone.
notify-source: Specifies the local source address. You also have the option to specify the UDP port that is used to send notify messages. The local source address must appear in the masters list of the slave server or in the allow-notify list. The slave should also be configured to receive notify messages from this address. Notify-source specified at the server level is overridden by the settings of this zone.
transfer-source: Specifies the local addresses that are bound to the IPv4 TCP connections used by the zones that are transferred inbound by the server. It also specifies the source IPv4 address and, optionally, the UDP port. The UDP port is used to refresh queries and forward any dynamic updates.
If you have not set a value, this option defaults to a system-controlled value usually the address of the interface closest to the remote end.
Transfer-source specified at the server level is overridden by the settings of this zone.
zone-statistics: Specifies the statistical information that is dumped to the statistics-file for all zones in the server. Values can be either Yes or No. If you set the value to Yes, the server collects statistical data on all zones in the server. Zone-statistics specified at the server level is overridden by the settings of this zone.
Click
after the additional option(s) are selected.Click
to complete the modify process. A confirmation message displays that the modify process succeeded.A DNS server can be configured to serve only the queries by specifying the role of a zone as passive, secondary, or passive secondary.
To associate the existing DNS zone to a specific DNS server and specify the role of the zone:
In the iManager DNS role, select the Zone Management task.
From the list of operations, select
.Select the zone you want to modify.
Specify the Authoritative DNS server for this zone, which is the zone for the specific DNS server.
Click
.In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the Delete DNS Zone window.Select the DNS zones that are to be deleted.
To delete all the Zone objects in the list, click the top-level check box.
Click
.Select the zones whose sub-zones are to be deleted.
To delete all the sub-zone objects in the list, click the top-level check box.
Click
.In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the Import DNS Zone window.Specify or browse the eDirectory context where the zone is to be created.
Select a designated DNS server distinguished name.
This server will subsequently manage the zone data.
Select the
as Primary (default) or Secondary. If you select Secondary as the Zone type, specify the IP address of the zone.Specify or browse to select the DNS Bind File location.
Click
.If the import operation encounters any problems, you can view the error details by downloading the log file. Also, if any of the resource records are ignored because of this problem, you can create them again by using the task in Creating Resource Records.
In iManager, click
to open the Zone Management window in the main panel.From the drop-down menu, select
and click to open the Export DNS Zone window.From the drop-down menu, select the DNS Zone to which the file will be exported.
Click
.Click the
to open the File Download dialog box.Select
, then click .Specify the name of the file or browse to select it, then click
.Click
.An RRSet object represents an individual domain name within a DNS zone. Each RRSet object has one or more resource records beneath it that contain additional information about the domain.
The most common resource records are Address (A) records, which map a domain name to an IP address, and Pointer (PTR) records, which map an IP address to a domain name within an IN-ADDR.ARPA zone.
Creation, Modification, or Updating the resource records is not supported for a Forward Zone.
NOTE:After creating, modifying, or updating the resource records, the data needs to be refreshed by clicking the
button. Without refreshing, the SOA for zone is not updated and the server continues to use old data.The Resource Record Management role consists of the following tasks:
A resource record is a piece of information about a domain name. Each resource record contains information about a particular piece of data within the domain.
To create a new resource record:
In iManager, click
t to open the Resource Record Management window in the main panel.From the drop-down menu, select
and click to open the Create Resource Record window.From the drop-down menu, select the domain name where the resource record is to be created, then click
.Resource records cannot be created in a secondary zone.
Specify the owner name under which you want to create the resource record or click the Object Selector icon to search for an existing owner name.
If the owner name is not specified, the resource record is created under @.
Select the
.A: Maps a domain name to an IP address. If you select this option, you must specify the 32-bit IPv4 address that will map to the associated domainA.
CNAME: Specifies the canonical or primary name for the owner. Because the owner name is an alias, you must specify the domain name of the aliased host if you select this option.
Others: From the Others drop-down menu, select the resource record type (RR Type) and specify the appropriate resource record data corresponding to the type chosen.
Click
.Click
after the resource record is created.Click
to automatically increment the serial number and complete the task.For more information on resource record types, see Section A.2, Types of Resource Records.
In iManager, click
to open the Resource Record Management window in the main panel.Select
from the drop-down menu and click to open the Modify RRSet - Resource Record window.From the
drop-down menu, select the domain that contains the host or RRSet.Resource records cannot be created in a secondary zone.
Specify or search to select the values for the:
and fields.To use the search feature to select these values:
Click the
icon to open the Object Selector window.Select the
type from the drop-down menu, select the number of search results to be displayed per page, click , then click the hostname.This automatically fills in the
> and fields.Click
to modify the resource record data.Modify the resource record data for all but the following types of resource records:
A (or IPv4)AAAA (or IPv6)A6
PTR
Specify new comments or modify existing comments for the resource record data.
Click
to save the changes.You can delete one, more than one, or all resource records and RRSets, using the multi-select deletion feature in iManager.
In iManager, click
to open the Resource Record Management window in the main panel.From the drop-down menu, select
and click to open the Delete RRSet - Resource Record window.From the
drop-down menu, select the domain that contains the host or RRSet.Delete one or more RRSets:
To search for RRSets by owner name, specify the name of the RRSet owner.
Select the RRSet option from the
drop-down menu.Click
to list the available RRSets that match the specified owner name.To delete all RRSets listed, click the top-level check box and click
. To delete one or more RRSets, click the corresponding check boxes and click .Delete one or more resource records:
To search for a resource record by owner name, specify the name of the Resource Record owner.
Select Resource record from the
drop-down menu.Select the resource record type from the
drop-down menu.Click
to list the available resource records that match the specified owner name.To delete all resource records listed, click the top-level check box and click . To delete one or more resource records, click the corresponding check boxes and click .NOTE:When the A and PTR type resource records are deleted, the corresponding PTR and A resource records also deleted.
The DNS Key Management role consists of tasks that allow you to create, modify, and delete DNS Key objects.A DNS Key provides a means of authentication for dynamic DNS updates and for queries to a secured DNS Server. A DNS Key uses shared secret keys as a cryptographically secure means of authenticating a DNS update or query. Only HMAC-MD5 algorithm is supported for DNS Key management. HMAC-MD5 keys must be between 1 and 512 bits. For more information, see the dnssec-keygen manpage.
NOTE:The DNS key option is supported for Linux DNS only.
-a: RSA, RSAMD5, DH, DSA, RSASHA1 are not supported by novell-named.
-n: ZONE nametype.
-f: setting the flag in DNSKEY record.
-p: protocol support is not affirmed as it is used in conjunction with DNSKEY for DNSSEC.
Example: dnssec-keygen -v Usage: dnssec-keygen -a HMAC-MD5 -b 218 -n HOST mykey Version: 9.3.4 Required options: -a algorithm: RSA | RSAMD5 | DH | DSA | RSASHA1 | HMAC-MD5 -b key size, in bits: RSAMD5: [512..4096] RSASHA1: [512..4096] DH: [128..4096] DSA: [512..1024] and divisible by 64 HMAC-MD5: [1..512] -n nametype: ZONE | HOST | ENTITY | USER | OTHER name: owner of the key
The following sections provides information on DNS Key management:
In iManager, click
> to open the window in the main panel.From the drop-down menu, select
and click to open the window.Specify a name to identify the DNS key in the
field.Specify the name of the
. The HMAC-MD5 algorithm is the only supported algorithm for a DNS key.Specify the secret key used by the DNS server to encrypt/decrypt the hashed data. Secret-456errt4545= is the secret key generated by dnssec-keygen.
The secret key provided must be Base64 encoded, else the DNS server fails to start.
Specify or browse to select the
.Click
. The DNS key is now created.Example: DNS KeyName-Key1,Alorithm-HMAC-MD5,Key Secret-456errt4545=
In iManager, click DNS > DNS Key to open the
window in the main panel.From the drop-down menu, select
and click to open the View/Modify DNS Key window.From the drop-down menu, select the DNS Key that you want to view/modify, then click
to open the window.Modify the attributes such as
, and the associated comments, then click .In iManager, click DNS > DNS Key to open the DNS Key Management window in the main panel.
From the drop-down menu, select
and click to open the Delete DNS Key window.Select the DNS key that is to be deleted. Click
. The DNS key is now deleted.To delete multiple DNS keys, click the top-level folder. Click
.NOTE:Deleting DNS key objects, deletes the references to key objects (if any) in Zone and DNS server objects.