Paolo Galtieri wrote:
dig -x 172.16.96.20
returns
; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20
;; global options: +cmd
;; connection timed out; no servers could be reached
but
dig
centos8-opstcore-vm.homenet172-16-96.com
returns
; <<>> DiG 9.16.24-RH <<>>
centos8-opstcore-vm.homenet172-16-96.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31140
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com. IN A
;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com. 259200 IN A 172.16.96.20
;; Query time: 2 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Feb 22 16:04:46 PST 2022
;; MSG SIZE rcvd: 85
Forward and reverse DNS resolution uses two different set of record
files. For instance, if you were using BIND as your name server, then
there's be one file that controls what IPs belong to which name, and
another which controls what name is returned for an IP.
Are you using BIND?
Have you got the forward and reverse record files?
Have they both got the records you expect to find?
Does the named.conf file correctly reference both record files?
If you use something other than BIND, let us know. I didn't notice you
saying what you used in prior messages.
--
uname -rsvp
Linux 3.10.0-1160.53.1.el7.x86_64 #1 SMP Fri Jan 14 13:59:45 UTC 2022 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.