Setup DNS on gridctrl


Now to configure the named service using the manual (RHEL 5.4 Deployment Guide: Chapter 17. Berkeley Internet Name Domain (BIND) in order to solve the problem encountered in 11G OCM Patch OEM 10.2.0.5 (2).

Setting Up the NAMED Configure File

Check for CHROOT

According to 17.1.3. BIND as a Nameserver, I need to check to see if chroot is enabled for named.

If you have installed the bind-chroot package, the BIND service will run in the /var/named/chroot environment. All configuration files will be moved there. As such, named.conf will be located in /var/named/chroot/etc/named.conf, and so on.

I do have this enabled – see the following:

[root@gridctrl ~]# rpm -qa bind-chroot
bind-chroot-9.3.6-4.P1.el5

Create the named.conf

From my reading of 17.2. /etc/named.conf, I only had to create /var/named/chroot/etc/named.conf with the following:

zone "yaocm.id.au" IN {
	type master;
	file "/var/named/yaocm.id.au.zone";
	allow-update { none; };
};
zone "2.1.10.in-addr.arpa" IN {
	type master;
	file "/var/named/yaocm.id.au.rr.zone";
	allow-update { none; };
};

I have a very simple namespace of one (1) level and therefore one (1) zone: yaocm.id.au. And all of the IP addresses are in the subnet of 10.1.2.0/24.

Create the Zone File

From my reading of 17.3. Zone Files, I need to create a file called /var/named/chroot/var/named/yaocm.id.au.zone. I just used the 17.3.3. Example Zone File to come up with:

$TTL 86400
@	SOA	dns1.yaocm.id.au.	hostmaster.yaocm.id.au. (
		2009122701 ; serial
		21600      ; refresh after 6 hours
		3600       ; retry after 1 hour
		604800     ; expire after 1 week
		86400 )    ; minimum TTL of 1 day
;
; Nameservers
;
	NS	dns1.yaocm.id.au.
dns1	A	10.1.2.200
;
;
@	MX	10	mail.yaocm.id.au.
mail	A	10.1.2.200
;
;
; There are only (4) hosts in the network:
;
gridctrl	A	10.1.2.200 
penrith1	A	10.1.2.201 
penrith2	A	10.1.2.202 
bankstwn	A	10.1.2.203 
;
; Virtual IP for the RAC
;
penrith1-vip	A	10.1.2.211 
penrith2-vip	A	10.1.2.212 
;
;

Create Reverse Name Resolution Zone File

Using the example from 17.3.4. Reverse Name Resolution Zone Files, I created /var/named/chroot/var/named/yaocm.id.au.rr.zone:

$TTL 86400
@	SOA	dns1.yaocm.id.au.	hostmaster.yaocm.id.au. (
		2009122701 ; serial
		21600      ; refresh after 6 hours
		3600       ; retry after 1 hour
		604800     ; expire after 1 week
		86400 )    ; minimum TTL of 1 day
;
; Nameservers
;
	NS	dns1.yaocm.id.au.
dns1	A	10.1.2.200
;
200	IN	PTR	gridctrl.yaocm.id.au.
201	IN	PTR	penrith1.yaocm.id.au.
202	IN	PTR	penrith2.yaocm.id.au.
203	IN	PTR	bankstwn.yaocm.id.au.
;
211	IN	PTR	penrith1-vip.yaocm.id.au.
212	IN	PTR	penrith2-vip.yaocm.id.au.
;

Starting the NAMED service

Starting the NAMED service manually

I used the service command (use info service to find details) to start the service:

[root@gridctrl ~]# service named start
Starting named:                                            [  OK  ]

Validating the NAMED configuration

To validate the configuration, I ran two (2) tests using the nslookup command: name lookup; and reverse name lookup.

[root@gridctrl ~]# nslookup 10.1.2.200
Server:         127.0.0.1
Address:        127.0.0.1#53

200.2.1.10.in-addr.arpa name = gridctrl.yaocm.id.au.

[root@gridctrl ~]# nslookup 10.1.2.212
Server:         127.0.0.1
Address:        127.0.0.1#53

212.2.1.10.in-addr.arpa name = penrith2-vip.yaocm.id.au.

Having the NAMED service start automatically

I used the chkconfig command to have the named service start on boot-up:

[root@gridctrl ~]# chkconfig named on
[root@gridctrl ~]# chkconfig --list named
named           0:off   1:off   2:on    3:on    4:on    5:on    6:off

Line #1 turns the automatic start-up on for named, while line #2 verifies that the service will start at runlevels 2 to 5 (inclusive).

All Done

I am rapidly becoming a Red-Hat System Administrator. I hope this fixes the OEM configuration problem.

Advertisements

4 thoughts on “Setup DNS on gridctrl

  1. 11G OCM Patch OEM 10.2.0.5 (3) « Yet Another OCM

  2. I also had to set up the DNS client as well:

    [oracle@gridctrl ~]$ cat /etc/resolv.conf
    search yaocm.id.au
    nameserver 127.0.0.1
    nameserver 10.1.1.1
    
  3. Review of OEM 10.2.0.5 Installation « Yet Another OCM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s