Comment 16 for bug 1864256

Yesterday, I had host name resolution shortly working after fiddling with nsswitch.conf IIRC. I noticed that I had also an /etc/nsswitch.conf.rpmnew file with date: 2020-08-06.
After rebooting my resolving of inner VPN hosts does not work any more. Unfortunately, I'm not experienced in this area, apologies for the vague report, but I hope it might give you some hints.
It could be that in the past I made changes to the nsswitch.conf, and that that file was not updated any more because of this. I have been using and updating my current system from many Fedora version back.

My nsswitch.conf.rpmnew contains this line:
hosts: files dns myhostname

My current is now a copy of the nsswitch.conf.rpmnew, but I modified the hosts: line to:
hosts: files resolve myhostname
In this configuration inner VPN host names do not resolve

Just now I changed the line back to:
hosts: files dns myhostname
I did:
# systemctl restart NetworkManager
Connected the VPN again via the GUI (first time I got an error, second time was successful)
# resolvectl dns
Global: 192.168.253.4 192.168.253.5 84.116.46.21 84.116.46.20
Link 2 (enp35s0): 84.116.46.21 84.116.46.20
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 5 (virbr1):
Link 6 (virbr1-nic):
# resolvectl domain
Global:
Link 2 (enp35s0): ~.
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 5 (virbr1):
Link 6 (virbr1-nic):
But the dns does not work for VPN internal hosts.