Manage DNS and NIS Name Service |
The Manage DNS, NIS Name Service page enables you to manage name resolution and authentication on the filer. Data ONTAP uses the /etc/hosts configuration file, Network Information Service (NIS), and Domain Name System (DNS) to resolve host names and the hosts, passwd, netgroup, group, and shadow files to authenticate users and group information.
Data ONTAP searches for host and user information in the following order:
Files in the /etc directory of the filer's default volume
NIS
DNS (for host-name resolution only)
You can manage the way Data ONTAP looks up host and user information by changing the default name search order and by maintaining and updating the /etc/hosts file.
The following is a list of fields that can be configured for Name Service, DNS, and NIS, and a description of each field.
Specifies the order Data ONTAP searches for host and user information: by the /etc files, NIS, or DNS.
If NIS and DNS are not enabled, or if you select Files as your first search order criteria for Hosts, you must maintain the /etc/hosts file so that Data ONTAP can resolve host names used in any of the following files:
/etc/rc
/etc/syslog.confg
/etc/dgateways
/etc/exports
/etc/netgroup
/etc/hosts.equiv
If you use the /etc/hosts file, you must ensure that it is kept up to date.
Specifies the order Data ONTAP searches for password information: by the /etc files or NIS.
Specifies the order Data ONTAP searches for shadow information: by the /etc files or NIS..
The shadow password database contains encrypted password information and password aging information used in CIFS and (PC)NFS environments.
Specifies the order Data ONTAP searches for group information: by the /etc files or NIS.
Specifies the order Data ONTAP searches for netgroup information: by the /etc files or NIS.
Specifies whether DNS is enabled on the filer.
Using DNS, you no longer have to update the filer's /etc/hosts file in the root volume every time you add a new host to the network, unless you specify files as the first search order in the Hosts field for the Name Service.
In a cluster, the DNS Enabled field must have the same value on both filers and the Domain Name must be the same on both filers for takeover to occur properly.
Specifies the DNS domain name to be used for the filer.
In a cluster, the DNS Enabled field must have the same value on both filers and the Domain Name must be the same on both filers for takeover to occur properly.
Specifies up to three name server host IP addresses that the filer can query.
Up to three name servers can be listed; the filer queries them in the order listed. When a query to a name server on the list times out, the filer moves to the next one until it gets to the last. It then restarts from the first server retrying all the name servers until a maximum number of retries are made.
Specifies the search list for host-name lookup.
The search list is normally determined from the local domain name; by default, it begins with the local domain name, then successive parent domains that have at least two components in their names. This can be changed by listing the desired domain search path, which is limited to six domains with a total of 256 characters.
Most resolver queries attempt to use each component of the search path in turn until a match is found. Note that this process might be slow and generate heavy network traffic if the servers for the listed domains are not local, and that queries can time out if no server is available for one of the domains.
Specifies whether NIS is enabled on the filer.
Using NIS, you no longer have to update the filer's /etc/hosts file in the root volume every time you add a new host to the network, unless you specify files as the first search order in the Hosts field for the Name Service.
The filer includes NIS client capabilities. This means that it can query NIS servers for host-name-to-IP-address and IP-address-to-host-name translation services.
The filer uses the following NIS maps:
hosts.byname
hosts.byaddr
passwd.byname
passwd.byuid
passwd.adjunct
group.byname
group.bygid
netgroup.byhost
Shadow password information is obtained from the passwd.byname map.
In a cluster, the NIS Enabled field must have the same value on both filers and the Domain Name must be the same on both filers for takeover to occur properly.
Specifies the NIS domain name to be used for the filer.
In a cluster, the NIS Enabled field must have the same value on both filers and the Domain Name must be the same on both filers for takeover to occur properly.
Specifies the list of NIS servers to be used by the filer. An asterisk (*) specifies binding by broadcast.
Specifies that the local caching of the NIS group files should be enabled.
Specifies the hours of the day when the local NIS group cache should be updated.