On 21 Feb 2022, at 20:15, Paolo Galtieri <pgaltieri(a)gmail.com&gt; wrote: Folks, I have 3 Linux systems, one running F31 and 2 running F34. On one of the F34 systems I have a local DNS server running. This has worked fine in the past, but now I'm seeing strangeness on the 2 F34 systems. I added a host to the DNS server for normal lookup and reverse lookup. On the F31 system both: host centos8-opstcore-vm.homenet172-16-96.com and host 172.16.96.20 work. The first returns 172.16.96.20 and the second returns centos8-opstcore-vm.homenet172-16-96.com. On the F34 which is the DNS server the first works, but the second fails with: Host 20.96.16.172.in-addr.arpa. not found: 3(NXDOMAIN) On the other F34 system I get: host 172.16.96.20 ;; connection timed out; no servers could be reached The interface has the DNS server pointing to the correct system. If I run: nslookup > server 192.168.10.66 Default server: 192.168.10.66 Address: 192.168.10.66#53 > 172.16.96.20 20.96.16.172.in-addr.arpa name = centos8-opstcore-vm.homenet172-16-96.com. >

Then it works. What do I need to do on F34 systems to get DNS lookups working?

Any help is appreciated. Paolo _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)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

On Mon, Feb 21, 2022 at 4:52 PM Barry <barry(a)barrys-emacs.org&gt; wrote: > On 21 Feb 2022, at 20:15, Paolo Galtieri <pgaltieri(a)gmail.com&gt; wrote: > > Folks, >  I have 3 Linux systems, one running F31 and 2 running F34.  On one of the F34 systems I have a local DNS server running.  This has worked fine in the past, but now I'm seeing strangeness on the 2 F34 systems. > > I added a host to the DNS server for normal lookup and reverse lookup.  On the F31 system both: > > host centos8-opstcore-vm.homenet172-16-96.com <http://centos8-opstcore-vm.homenet172-16-96.com> > > and > > host 172.16.96.20 > > work. The first returns 172.16.96.20 and the second returns centos8-opstcore-vm.homenet172-16-96.com <http://centos8-opstcore-vm.homenet172-16-96.com>;. > > On the F34 which is the DNS server the first works, but the second fails with: > > Host 20.96.16.172.in-addr.arpa. not found: 3(NXDOMAIN) > > On the other F34 system I get: > > host 172.16.96.20 > > ;; connection timed out; no servers could be reached > > The interface has the DNS server pointing to the correct system. If I run: > > nslookup > > server 192.168.10.66 > Default server: 192.168.10.66 > Address: 192.168.10.66#53 > > 172.16.96.20 > 20.96.16.172.in-addr.arpa    name = centos8-opstcore-vm.homenet172-16-96.com <http://centos8-opstcore-vm.homenet172-16-96.com>;. > > Nslookup has been replaced by the dig program. Barry > > Then it works. > > What do I need to do on F34 systems to get DNS lookups working? Might you be using systemd-resolved on the f34 to cache for you? What does resolvectl report?

Barry

> > Any help is appreciated. > > Paolo > In Fedora 33 DNS resolution was changed (1)adding a DNS server to /etc/resolv.conf using systemd-resolve. There is still an /etc/resolv.conf and it is configured to use a name service running on a loopback device where a local DNS service is listening. # grep -v '#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search domain.com <http://domain.com> If you are using the NetworkManager service just add the DNS server address and it should start working.

Something like this "nmcli con mod $connectionName ipv4.dns "1.1.1.1 9.9.9.9".

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(a)lists.fedoraproject.org To unsubscribe send an email tousers-leave(a)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.fedora... Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

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:

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(a)lists.fedoraproject.org > To unsubscribe send an email tousers-leave(a)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.fedora... > Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org To unsubscribe send an email tousers-leave(a)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.fedora... Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

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