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
; <<>> 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
Paolo
You can see running dig followed by an IP doesn't return anything, to
do a reverse DNS lookup, or to resolve the hostname from the IP, you
can see in the second example dig -x followed by the IP returns the
hostname one.one.one.one.
$ dig 1.1.1.1
; <<>> DiG 9.16.24-RH <<>> 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42214
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1. IN A
;; AUTHORITY SECTION:
. 60 IN SOA a.root-servers.net <http://a.root-servers.net>.
nstld.verisign-grs.com <http://nstld.verisign-grs.com>. 2022022101
1800 900 604800 86400
;; Query time: 241 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:50 EST 2022
;; MSG SIZE rcvd: 111
# dig -x 1.1.1.1
; <<>> DiG 9.16.24-RH <<>> -x 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63485
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1.in-addr.arpa. IN PTR
;; ANSWER SECTION:
1.1.1.1.in-addr.arpa. 1131 IN PTR one.one.one.one.
;; Query time: 74 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:57 EST 2022
;; MSG SIZE rcvd: 78
; <<>> DiG 9.16.24-RH <<>> 172.16.96.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;172.16.96.20. IN A
;; AUTHORITY SECTION:
. 6751 IN SOA a.root-servers.net
<http://a.root-servers.net>. nstld.verisign-grs.com
<http://nstld.verisign-grs.com>. 2022022101 1800 900 604800 86400
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:39:02 PST 2022
;; MSG SIZE rcvd: 116
dig centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>
; <<>> DiG 9.16.24-RH <<>>
centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26457
;; 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
<http://centos8-opstcore-vm.homenet172-16-96.com>. IN A
;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>. 4778 IN A
172.16.96.20
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:40:16 PST 2022
;; MSG SIZE rcvd: 85
I tried stopping and restarting systemd-resolved to no avail as
well as restarting the network interface also to no avail.
What's curious is for example
host 192.168.10.2 will return a host name most likely because it's
cached.
host 172.16.96.20 results in host not found on one F34 system and
no servers could be reached on the other F34 system
I ran wireshark on the DNS server and it showed the query to
127.0.0.53 with the hostname and a response of the ip address.
But a query to 127.0.0.53 with the ip address returned a not found
error.
At first I didn't like this new way to manage DNS, but I am
finding some of the features to work very well. Like the split
dns feature is working really well with the multiple vpn clients
run simultaneously, no more hacking on /etc/resolv.conf each time
a new VPN is started, it just works.
1 - https://fedoraproject.org/wiki/Changes/systemd-resolved
Regards,
-Jamie
_______________________________________________
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report
it:https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report
it:https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
