On 21 Feb 2022, at 20:15, Paolo Galtieri pgaltieri@gmail.com 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.
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
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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