Comment 13 for bug 1864256

I did some testing with the following command:
# resolvectl dns

This are the results is different situations:
No VPN, IPv6 enabled (automatic):
# resolvectl dns
Global: 84.116.46.21 84.116.46.20 2001:b88:1002::10 2001:b88:1202::10 2001:730:3e42:1000::53
Link 2 (enp35s0): 84.116.46.21 84.116.46.20 2001:b88:1002::10 2001:b88:1202::10 2001:730:3e42:1000::53
Link 3 (virbr1):
Link 4 (virbr1-nic):
Link 5 (virbr0):
Link 6 (virbr0-nic):

VPN enabled, IPv6 enabled (automatic):
# resolvectl dns
Global: 192.168.253.4 192.168.253.5 84.116.46.21 84.116.46.20 2001:b88:1002::10 2001:b88:1202::10 2001:730:3e42:1000::53
Link 2 (enp35s0): 84.116.46.21 84.116.46.20
Link 3 (virbr1):
Link 4 (virbr1-nic):
Link 5 (virbr0):
Link 6 (virbr0-nic):

No VPN, IPv6 disabled:
# resolvectl dns
Global: 84.116.46.21 84.116.46.20
Link 2 (enp35s0): 84.116.46.21 84.116.46.20
Link 3 (virbr1):
Link 4 (virbr1-nic):
Link 5 (virbr0):
Link 6 (virbr0-nic):

VPN enabled, IPv6 disabled:
# 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 (virbr1):
Link 4 (virbr1-nic):
Link 5 (virbr0):
Link 6 (virbr0-nic):

The DNS servers provided by the VPN are: 192.168.253.4,192.168.253.5
My /etc/resolv.conf is a symbolic link to /var/run/NetworkManager/resolv.conf
I also upgraded from Fedora 32 to Fedora 33.
I still have another computer running Fedora 32, where the DNS for resolving VPN host works fine. So I can do some tests or comparisons if this would help.