Gns

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 1

gns

DNS Configuration for Domain Delegation to Grid Naming Service


If you plan to use GNS, then before Oracle Grid Infrastructure installation, you
must
configure your domain name server (DNS) to send to GNS name resolution requests
for the subdomain GNS serves, which are the cluster member nodes. The following is
an overview of what needs to be done for domain delegation. Your actual procedure
may be different from this example.
Configure the DNS to send GNS name resolution requests using delegation:
1. In the DNS, create an entry for the GNS virtual IP address, where the address
uses
the form gns-server.CLUSTERNAME.DOMAINNAME. For example, where the

cluster name is mycluster, and the domain name is example.com, and the IP
address is 192.0.2.1, create an entry similar to the following:
mycluster-gns.example.com A 192.0.2.1
The address you provide must be routable.
2. Set up forwarding of the GNS subdomain to the GNS virtual IP address, so that
GNS resolves addresses to the GNS subdomain. To do this, create a BIND
configuration entry similar to the following for the delegated domain, where
cluster01.example.com is the subdomain you want to delegate:
cluster01.example.com NS mycluster-gns.example.com
3. When using GNS, you must configure resolve.conf on the nodes in the cluster
(or the file on your system that provides resolution information) to contain name
server entries that are resolvable to corporate DNS servers. The total timeout
period configured—a combination of options attempts (retries) and options
timeout (exponential backoff)—should be less than 30 seconds. For example,
where xxx.xxx.xxx.42 and xxx.xxx.xxx.15 are valid name server addresses in your
network, provide an entry similar to the following in /etc/resolv.conf:
options attempts: 2
options timeout: 1
search cluster01.example.com example.com
nameserver xxx.xxx.xxx.42
nameserver xxx.xxx.xxx.15
/etc/nsswitch.conf controls

name service lookup order. In some system


configurations, the Network Information System (NIS) can cause problems with
Oracle SCAN address resolution. Oracle recommends that you place the nis entry
at the end of the search list. For example:
/etc/nsswitch.conf
hosts: files dns nis
2.7.6 Grid Naming Service Configuration Example
If you use GNS, then you need to specify a static IP address for the GNS VIP
address,
and delegate a subdomain to be delegated to that static GNS IP address.
As nodes are added to the cluster, your organization's DHCP server can provide
addresses for these nodes dynamically. These addresses are then registered
automatically in GNS, and GNS provides resolution within the subdomain to cluster
node addresses registered with GNS.
Because allocation and configuration of addresses is performed automatically with
GNS, no further configuration is required. Oracle Clusterware provides dynamic
network configuration as nodes are added to or removed from the cluster. The
following example is provided only for information.
With a two node cluster where you have defined the GNS VIP, after installation you
might have a configuration similar to the following for a two-node cluster, where
the
cluster name is mycluster, the GNS parent domain is example.com, the subdomain

You might also like