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.
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.