DNS configuration

-

 [root@Node1 ~]# 

[root@Node1 ~]# cat /etc/resolv.conf 

# Generated by NetworkManager

search oracle.com

nameserver 192.168.0.1

options timeout:1

options attempts:5

[root@Node1 ~]# 

[root@Node1 ~]# 

[root@Node1 ~]# 

[root@Node1 ~]# 

[root@Node1 ~]# cat /etc/named.conf

// named.conf

//

// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS

// server as a caching only nameserver (as a localhost DNS resolver only).

//

// See /usr/share/doc/bind*/sample/ for example named configuration files.

//

// See the BIND Administrator’s Reference Manual (ARM) for details about the

// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html


options {

listen-on port 53 { 127.0.0.1; 192.168.0.1; };

listen-on-v6 port 53 { ::1; };

directory "/var/named";

dump-file "/var/named/data/cache_dump.db";

statistics-file "/var/named/data/named_stats.txt";

memstatistics-file "/var/named/data/named_mem_stats.txt";

recursing-file "/var/named/data/named.recursing";

secroots-file "/var/named/data/named.secroots";

allow-query { localhost; 192.168.0.0/24; };


/*

– If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.

– If you are building a RECURSIVE (caching) DNS server, you need to enable

recursion.

– If your recursive DNS server has a public IP address, you MUST enable access

control to limit queries to your legitimate users. Failing to do so will

cause your server to become part of large scale DNS amplification

attacks. Implementing BCP38 within your network would greatly

reduce such attack surface

*/

recursion yes;

dnssec-enable yes;

dnssec-validation yes;


/* Path to ISC DLV key */

bindkeys-file "/etc/named.root.key";


managed-keys-directory "/var/named/dynamic";


pid-file "/run/named/named.pid";

session-keyfile "/run/named/session.key";

};


logging {

channel default_debug {

file "data/named.run";

severity dynamic;

};

};


zone "." IN {

type hint;

file "named.ca";

};


zone "oracle.com" IN {

type master;

file "oracle.com.zone";

allow-update { none; };

};


zone "0.168.192.in-addr.arpa." IN {

type master;

file "0.168.192.in-addr.arpa";

allow-update { none; };

};


include "/etc/named.rfc1912.zones";

include "/etc/named.root.key";

[root@Node1 ~]# 

[root@Node1 ~]# 

[root@Node1 ~]# 

[root@Node1 ~]# cat /var/named/oracle.com.zone 

$TTL 86400

@ IN SOA mysql.oracle.com. root.oracle.com. (

    2014051001 ; serial

    3600       ; refresh

    1800       ; retry

    604800     ; expire

    86400      ; minimum

)

@ IN NS mysql.oracle.

localhost IN A 127.0.0.1

Node1 IN A 192.168.0.101

Node2 IN A 192.168.0.102

Node1-priv IN A 192.168.10.101

Node2-priv IN A 192.168.10.102

Node1-vip IN A 192.168.0.103

Node2-vip IN A 192.168.0.104

rac-scan IN A 192.168.0.105

rac-scan IN A 192.168.0.106

rac-scan IN A 192.168.0.107

[root@Node1 ~]# 

[root@Node1 ~]# cat /var/named/0.168.192.in-addr.arpa 

$TTL 86400

@ IN SOA Node1.oracle.com. root.oracle.com. (

2

3H

1H

1W

1H )

@ IN NS Node1.oracle.com.

@ IN PTR oracle.com.

Node1 IN A 192.168.0.101

rac-scan IN A 192.168.0.105

rac-scan IN A 192.168.0.106

rac-scan IN A 192.168.0.107

101 IN PTR Node1.oracle.com.

102 IN PTR Node2.oracle.com.

105 IN PTR rac-scan.oracle.

106 IN PTR rac-scan.oracle.

107 IN PTR rac-scan.oracle.

[root@Node1 ~]# 

[root@Node1 ~]# nslookup Node1.oracle.com

;; connection timed out; no servers could be reached


[root@Node1 ~]#  




[root@Node1 ~]# systemctl status firewalld

● firewalld.service - firewalld - dynamic firewall daemon

   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)

   Active: inactive (dead) since Sat 2024-12-14 08:18:37 EST; 6min ago

     Docs: man:firewalld(1)

  Process: 1079 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)

 Main PID: 1079 (code=exited, status=0/SUCCESS)


Dec 14 08:10:50 Node1.oracle.com systemd[1]: Starting firewalld - dynamic firewall daemon...

Dec 14 08:10:52 Node1.oracle.com systemd[1]: Started firewalld - dynamic firewall daemon.

Dec 14 08:10:52 Node1.oracle.com firewalld[1079]: WARNING: AllowZoneDrifting is enabled. This is considered an insecure configuration option. It will be removed in a future release. Please consider disabling it>

Dec 14 08:18:37 Node1.oracle.com systemd[1]: Stopping firewalld - dynamic firewall daemon...

Dec 14 08:18:37 Node1.oracle.com systemd[1]: firewalld.service: Succeeded.

Dec 14 08:18:37 Node1.oracle.com systemd[1]: Stopped firewalld - dynamic firewall daemon.


 

[root@Node1 ~]# 

[root@Node1 ~]# systemctl status named

● named.service - Berkeley Internet Name Domain (DNS)

   Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled)

   Active: active (running) since Sat 2024-12-14 08:15:48 EST; 10min ago

  Process: 5930 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)

  Process: 5928 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SU>

 Main PID: 5932 (named)

    Tasks: 5 (limit: 22834)

   Memory: 20.4M

   CGroup: /system.slice/named.service

           └─5932 /usr/sbin/named -u named -c /etc/named.conf


Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving './NS/IN': 2001:500:2d::d#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving 'Node1.oracle/A/IN': 2001:500:2d::d#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving 'Node1.oracle/AAAA/IN': 2001:500:2d::d#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving 'Node1.oracle/A/IN': 2001:503:c27::2:30#53

Dec 14 08:15:48 Node1.oracle.com named[5932]: network unreachable resolving 'Node1.oracle/AAAA/IN': 2001:503:c27::2:30#53

Dec 14 08:15:58 Node1.oracle.com named[5932]: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out

Dec 14 08:15:58 Node1.oracle.com named[5932]: resolver priming query complete


Comments

Post a Comment

Popular posts from this blog

MY NOTEPAD

-
set lines 200 pages 200; col END_TIME for a20; col ELAPSED_TIME for a25; col START_TIME for a20 SELECT T.SESSION_KEY, T.INPUT_TYPE, T.STATUS, T.SUM_BACKUP_PIECES_IN_GB, T.START_TIME, T.END_TIME, T.SECONDS ELAPSED_TIME FROM ( SELECT SESSION_KEY, INPUT_TYPE, STATUS, OUTPUT_BYTES/1024/1024/1024 SUM_BACKUP_PIECES_IN_GB, TO_CHAR (START_TIME, 'dd/mm/yyyy hh24:mi') START_TIME, TO_CHAR (END_TIME, 'dd/mm/yyyy hh24:mi') END_TIME, TIME_TAKEN_DISPLAY SECONDS FROM V$RMAN_BACKUP_JOB_DETAILS WHERE INPUT_TYPE='ARCHIVELOG' ORDER BY SESSION_KEY DESC) T WHERE ROWNUM <= 1; ================ ASM disk group free space ============== set sqlblanklines on set lines 180 set pages 999le col "Group Name" form a25 col "Disk Name" form a30 col "State" form a15 ...
Read more

Oracle OEM Holistic Patch

-
  Oracle OEM Holistic Patch  The Concept Starting with Oracle Enterprise Manager (OEM) 13.5 RU24 (October 2024), Oracle introduced the Holistic Patch for OEM — a unified patching model that consolidates several separate updates into a single coordinated package. Previously, administrators had to patch: * The OMS and Agents with the quarterly Release Update (RU). * OEM Application via the System Patch Bundle (SPB). * WebLogic CPU and JDK manually. There was an element of complication because of the need to keep the solution homogeneous. With the Holistic Patch, the last two steps are merged into a single patch bundle. Now we have a new Holistic patch for OEM that is released with each new OMS Release Update. Prerequisites Apply RU 24 Patch  PATCH 36761595  /later on all OMSes before applying Oct Holistic Patch   PATCH 37305292             (OR) Apply RU 25 Patch  PATCH 37057635  /later on all OMSes before applying ...
Read more

Upgrade Oracle 19c DB to 21c using Auto Upgrade utility inprogress

-
Image
  Upgrade Oracle 11g to 21c using AutoUpgrade utility: How do I upgrade Oracle database to 21c?  install the 21c oracle binaries into the server . Oracle Virtual Bix  Oracle Linux 7 Oracle Database 19c currently running Upgrading 19c database to 21c directly Oracle Database 19c on premises is available – and one of the key features is the new Auto Upgrade utility. In the following days I will publish several blog posts explaining and showcasing the new Auto Upgrade. What is the Auto Upgrade? The Oracle Database Auto Upgrade utility is a new tiny little command line tool which allows you to upgrade your databases in an unattended way. I call it the Hands-Free Upgrade. The new Auto Upgrade utility in Oracle 19che idea of the tool is to run the prechecks against multiple databases, fix 99% of the potential issues, set a restore point in case something goes wrong – and then upgrade your databases. And of course, do the post upgrade, recompilation and time zone adjustment. The...
Read more