[root@dlp ~]# systemctl enable --now named
If Firewalld is running, allow DNS service on port 53 for both TCP and UDP:
[root@dlp ~]# firewall-cmd --add-service=dns
success
[root@dlp ~]# firewall-cmd --runtime-to-permanent
success
Change your DNS settings to refer to your own DNS server (replace [enp1s0] with your network interface name):
[root@dlp ~]# nmcli connection modify enp1s0 ipv4.dns 10.0.0.30
[root@dlp ~]# nmcli connection down enp1s0; nmcli connection up enp1s0
Use the dig command to verify both forward and reverse DNS resolution. If you see an "ANSWER SECTION," that means the resolution is successful.
For Forward DNS Resolution:
[root@dlp ~]# dig dlp.emc.world.
Sample Output:
; <<>> DiG 9.16.23-RH <<>> dlp.emc.world.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22835
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: d58f0c16c9f22ca00100000061dcce5e3191581ecff49d44 (good)
;; QUESTION SECTION:
;dlp.emc.world. IN A
;; ANSWER SECTION:
dlp.emc.world. 86400 IN A 10.0.0.30
;; Query time: 1 msec
;; SERVER: 10.0.0.30#53(10.0.0.30)
;; WHEN: Tue Jan 11 09:25:02 JST 2022
;; MSG SIZE rcvd: 86
For Reverse DNS Resolution:
[root@dlp ~]# dig -x 10.0.0.30
Sample Output:
; <<>> DiG 9.16.23-RH <<>> -x 10.0.0.30
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39095
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 10c59ae3bdb46f280100000061dcce83a05df24daf8b8401 (good)
;; QUESTION SECTION:
;30.0.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
30.0.0.10.in-addr.arpa. 86400 IN PTR dlp.emc.world.
;; Query time: 4 msec
;; SERVER: 10.0.0.30#53(10.0.0.30)
;; WHEN: Tue Jan 11 09:25:39 JST 2022
;; MSG SIZE rcvd: 106
If the "ANSWER SECTION" is shown in both cases, it indicates successful name and address resolution using your BIND DNS server.