On 2/22/22 16:08, Paolo Galtieri wrote:
On 2/21/22 15:56, Jamie Fargen wrote:
dig 172.16.96.20
Do you mean dig -x 172.16.96.20
dig 1.1.1.1 doesn't return the host name:
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
;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com. 259200 IN A 172.16.96.20
Tim is correct.
If you are using a hosted nameserver you will have to contact them and
request a PTR record for 172.16.96.20 that points to
centos8-opstcore-vm.homenet172-16-96.com.
If you are managing your own nameserver and it uses BIND format you need
to have a zone file with the correct nameserver name(s).
$TTL 3d
$ORIGIN 16.172.in-addr.arpa.
@ IN SOA your.name.server. email.your.name.server. 1645631337
16384 2048 1048576 2560 ;; the @ record is all on one line
IN NS your.name.server.
20.96 IN PTR centos8-opstcore-vm.homenet172-16-96.com.
Hope this helps,
Mike Wright
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
