|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Data Service for Domain Name Service (DNS) Guide|
This section describes the steps to install DNS and to enable DNS to run as Oracle Solaris Cluster HA for DNS.
Oracle Solaris Cluster HA for DNS uses the Internet Domain Name Server (in.named) software that is bundled with the Solaris 8, Solaris 9, and Solaris 10 operating systems. See the in.named(1M) man page for information about how to set up DNS. The Oracle Solaris Cluster configuration involves the following differences.
The DNS database is located on the cluster file system, not a local file system.
A network resource (relocatable IP address), not the name of a physical host, identifies the name of a DNS server.
This name should be an IP address (logical hostname) that you set up when you install the Oracle Solaris Cluster software. See the Solaris Cluster Concepts Guide for Solaris OS document for details about network resources.
The DNS executable is bundled with the Solaris 8, Solaris 9, and Solaris 10 operating systems. Ensure that this executable is located in the /usr/sbin directory before you begin the installation.
See the Solaris Cluster Software Installation Guide for Solaris OS for information on how to set up cluster file systems.
# mkdir -p /global/dns/named
If you have already installed DNS, you can copy the existing named.conf or named.boot file to the /global/dns directory. Otherwise, create a named.conf file in this directory. See the in.named(1M) man page for information on the types of entries to place in named.conf or named.boot. Either the named.conf file or the named.boot file must exist. Both files can exist.
On all of the nodes or zones, edit the /etc/resolv.conf file to contain the network resource. The following example shows the entries for a four-node configuration (phys-schost-1, phys-schost-2, phys-schost-3, and phys-schost-4) with the logical hostname schost-1.eng.sun.com.
domain eng.sun.com ; schost-1.eng.sun.com (Only entry to be added if the file is already present.) nameserver 18.104.22.168 ; phys-schost-2.eng nameserver 22.214.171.124 ; phys-schost-3.eng nameserver 126.96.36.199 ; phys-schost-4.eng nameserver 188.8.131.52 ; phys-schost-1.eng nameserver 184.108.40.206
Make the network resource the first entry after the domain name. DNS attempts to use the addresses in the order that they are listed in the resolv.conf file to access the server.
Note - If the /etc/resolv.conf is already present on the nodes or zones, just add the first entry that shows the logical hostname in the preceding example. The order of the entries determines the order in which DNS tries to access the server.
In the following example, perform these steps.
Replace the IPaddress variable with your actual IP address, such as 220.127.116.11.
Replace the logical-hostname variable with your actual network resource (logical hostname).
127.0.0.1 localhost IPaddress logical-hostname
hosts: cluster files dns
The following example shows how to test DNS.
# /usr/sbin/in.named -c /global/dns/named.conf # nslookup phys-schost-1
Be sure to stop the in.named executable before you proceed.
# pkill -x in.named
If you installed the Oracle Solaris Cluster HA for DNS packages during your Oracle Solaris Cluster installation, go to Registering and Configuring Oracle Solaris Cluster HA for DNS. Otherwise, go to Installing the Oracle Solaris Cluster HA for DNS Packages.