Sunday, September 3, 2023

 ==>>How to configure the DNS server For RAC on the Linux server? <<===


If, are you looking to set up and configure a DNS server in your Linux environment? Look no further! This article will guide you through the process, providing step-by-step instructions to ensure a smooth and successful DNS configuration. Whether you're a beginner or an experienced user, you'll find the information you need right here. Let's find out how to configure DNS in Linux on Vm Machine.

This article shows how to configure DNS on a Linux machine

Step 1, firstly configure the Linux server on the VM machine install.


Step 2 -login on that server you have created for the DNS do the changes on the files accordingly .

[root@dns ~]# 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;10.10.1.101; }; =======> IP ADDRESS OF DNS SERVER.
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;any; }; ==================> MENTION any here.

/*

- 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 "example.com" IN {
type master;
file "forward.example.com";
allow-update { none; };

};
zone "1.10.10.in-addr.arpa" IN {
type master;
file "reverse.example.com";
allow-update { none; };

};

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

Step -3  This below snap is help to create the forward dns configure .


Step-4    This below snap is help to create the forward dns configure .


Step-5 

MAKE SURE owner and GROUP of above forward and reverse zone should be as follows
owner group
root  named

Step-6

TO VERIFY WHETHER ALL ENTRIES WORKING FINE AND NO SYNTEX ISSUE IN ABOVE FILES. 
=========================================================================
/usr/sbin/named-checkconf /var/named/reverse.example.com
named-checkzone example.com /var/named/forward.example.com
named-checkzone example.com /var/named/reverse.example.com

Step-7  add the DNS server ip in the all node resolv.conf files including the DNS server 

add in all node.
[root@node1 ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search example.com
nameserver 10.10.1.101

Step-8  start the NDS services.

[root@dns named]# systemctl start named

[root@dns named]# systemctl status named






Post DNS configuration Verify the resolve the scan name in my case i kept the scan name "myscan"

DNS server nslookup output 


                                         

Node 1 nslookup myscan output
                                         

Node 2 nslookup myscan output 



                                        




Thank you to All ....

Thank you for giving your valuable time to read the above information.






 




 

  













No comments:

Post a Comment