Scribd
Upload
13 views3 pages

Configuring BIND9 for DBLab DNS

Uploaded by

wikaka6903
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
13 views3 pages

Configuring BIND9 for DBLab DNS

Uploaded by

wikaka6903
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

DNS Server - [Link] ([Link].

com)

Node1 - [Link] ([Link])


Node2 - [Link] ([Link])

Node1 - [Link] ([Link])


Node2 - [Link] ([Link])

Scan IP
[Link] [Link]
[Link] [Link]
[Link] [Link]

Node1 - [Link] ([Link])


Node2 - [Link] ([Link])

##### RAC Node1 & Node2 Hardware Specification #####


Storage - 70GB
/ 23GB
/boot 1GB
/db01 30GB
swap - 16GB

##### Openfiler Specification #####


/ 10GB
1GB RAM
hostname - [Link]
[Link]

##### DNS Configuration #####


1. Install require package
#~ yum -y install bind

2. Enable DNS Service


#~ systemctl start named
#~ systemctl enable named
#~ systemctl status named

3. Allow DNS in Firewall


#~ firewall-cmd --permanent --add-service=dns
#~ firewall-cmd --reload
#~ firewall-cmd --list-all

4. Configuration
#~ vim /etc/[Link]
- Change this: listen-on port 53 (add DNS IP)
- Change this: allow-query to (any)

#~ vim /etc/[Link]
- Add these contents:

zone "[Link]" IN {
type master;
file "[Link]";
};

zone "[Link]" IN {
type master;
file "reverse.192.168.227";
};

5. Create necessary files


#~ vim /var/named/[Link]
- Add these contents:
$TTL 2D
@ IN SOA [Link]. [Link]. (
20240423; serial number
1H; refresh time
10M; retry time
1W; expire time
1D; MTTL for negative query
)

@ IN NS [Link].
[Link]. IN A [Link]

[Link]. IN A [Link]
[Link]. IN A [Link]

[Link]. IN A [Link]
[Link]. IN A [Link]

[Link]. IN A [Link]
[Link]. IN A [Link]
[Link]. IN A [Link]

[Link]. IN A [Link]
[Link]. IN A [Link]

#~ vim .var/named/reverse.192.168.227
- Add these contents

@ IN SOA [Link]. [Link]. (


20240423; serial number
1H; refresh time
10M; retry time
1W; expire time
1D; MTTL for negative query
)

@ IN NS [Link].

[Link].[Link]. IN PTR [Link].

[Link].[Link]. IN PTR [Link].


[Link].[Link]. IN PTR [Link].

[Link].[Link]. IN PTR [Link].


[Link].[Link]. IN PTR [Link].

[Link].[Link]. IN PTR [Link].


[Link].[Link]. IN PTR [Link].
[Link].[Link]. IN PTR [Link].

6. Verification
# named-checkconf /etc/[Link]
# named-checkconf /etc/[Link]
# named-checkzone [Link] [Link]
# named-checkzone [Link] reverse.192.168.227
# systemctl start named
# systemctl enable named

Common questions

Powered by AI

The DNS configuration includes multiple 'IN A' records for oracle19c-scan.dblab.com pointing to IPs 192.168.227.19, 192.168.227.20, and 192.168.227.21. This setup uses round-robin DNS, which distributes the network load across multiple IP addresses, thereby providing scalability. It also ensures redundancy, as failure of one IP does not disrupt the service availability due to automatic redirection to other IPs .

The firewall commands necessary for DNS service operation are 'firewall-cmd --permanent --add-service=dns' and 'firewall-cmd --reload'. These commands add a permanent rule to the firewall to allow DNS traffic through the system, ensuring DNS queries and responses can be properly communicated. The reload command then applies these changes immediately .

Node1 and Node2 are each assigned multiple IP addresses for various network roles. The addresses 192.168.227.15 and 192.168.227.16 serve as main host addresses. The VIP addresses 192.168.227.17 and 192.168.227.18 are used for failover purposes, enhancing high availability. Additionally, 172.16.227.15 and 172.16.227.16 are private addresses likely used for inter-node communication within a private network, separate from public access .

The hardware specification for both RAC Node1 and Node2 includes storage allocations of 70GB for general use, 23GB for /boot, 1GB for /db01, and 30GB for swap space, with a total swap allocation of 16GB. The identical configurations suggest balanced performance expectations across the nodes, ensuring redundancy and fault tolerance in the cluster setup .

The configuration of /etc/named.conf determines which IP addresses the DNS service listens to on port 53, and it controls which clients can query the DNS server. Setting the 'listen-on' directive with specific DNS IPs restricts access to the service, enhancing security against unauthorized access. The 'allow-query' setting to 'any' supports functionality by permitting queries from any client, thus providing flexibility but also potentially reducing strict access controls unless further refined .

The utilities named-checkconf and named-checkzone are used to verify the configuration and zone files in a DNS setup. named-checkconf checks the syntax and correctness of the named.conf and named.rfc1912.zones files, ensuring proper server setup. named-checkzone validates the structure and contents of the zone files like dblab.com.zone and reverse.192.168.227, ensuring they are correct and ensuring reliable domain name resolution .

The document outlines several key steps for configuring DNS: installing the required package using 'yum -y install bind', enabling the DNS service with 'systemctl start named' and 'systemctl enable named', allowing DNS through the firewall with 'firewall-cmd --permanent --add-service=dns' and 'firewall-cmd --reload', and configuring named.conf to listen on the correct port and allow queries. It also involves editing named.rfc1912.zones to add the domain zones and creating necessary zone files in /var/named/, followed by verifying configurations using 'named-checkconf' and 'named-checkzone' commands .

$TTL, set in the DNS zone file, determines the time-to-live for the DNS records, reflecting the duration a DNS record is cached by clients and servers. In this setup, it's set to 2 days, balancing between reduced DNS lookups (enhancing performance by minimizing query frequency) and slower propagation of DNS changes (potentially delaying the effect of updates or corrections across the network).

Reverse DNS is configured by mapping IP addresses to hostnames using PTR records in the reverse.192.168.227 zone file. Each IP, such as 192.168.227.100, is associated with a corresponding hostname like dnsrvr.dblab.com. Reverse DNS is important for validating the authenticity of servers, aiding in spam prevention, and providing a convenient way to resolve IP addresses back to human-readable domain names, which is especially useful in network troubleshooting and management .

Setting 'allow-query' to 'any' may expose the DNS server to potential abuse, such as DNS amplification attacks, where the server can be used to flood victims with traffic. To mitigate this, network administrators can implement firewalls to restrict incoming DNS requests to known sources, use rate limiting on query responses, and employ DNSSEC to ensure data authenticity, thus reducing the risk of being exploited by malicious entities .

You might also like