Openvpn's update-resolv-conf set the nameservers in the wrong order with openresolv

I wanted to switch from resolvconf to openresolv since openresolv seems more reliable.

I use Mullvad and set my nameserver to 100.64.0.1 as backup nameserver. Now I when use resolvconf and start OpenVPN, update-resolv-conf writes the nameserver to /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN# 127.0.0.53 is the systemd-resolved stub resolver.# run "resolvectl status" to see details about the actual nameservers.nameserver 10.5.0.1nameserver 100.64.0.1

The OpenVPN nameserver is the first one in the list, and I assume the DNS resolver listen to this nameserver before it listens to 100.64.0.1? When 10.5.0.1 fails it listens to 100.64.0.1? Or mainly listens to 10.5.0.1?

When I run OpenVPN with openresolv, my /etc/resolv.conf looks like this

# Generated by resolvconfnameserver 100.64.0.1nameserver 10.5.0.1

As you can see the order is different with openresolv. I want use openresolv and 10.5.0.1 as first nameserver in /etc/resolv.conf. Anyone know the solution?