Why QubesOS need some control over OpenVPN set ups? while other VPNs can work from the box? what is the sense of it?

I encountered an issue where the connection doesn’t work with mirage-firewall. However, when I connect directly to sys-net, it functions correctly.

Additionally, I’ve found that I must manually set the DNS server to 1.1.1.1 (or another address) in the resolv.conf file on the virtual machine I wish to use. If I don’t do this, nothing works.

Through this experience, I’ve learned that QubesOS indeed employs some unique DNS management strategies, which confirmed something I had suspected.

Now, I find myself in a country where popular VPN services are blocked. As a result, I’ve had to set up my own OpenVPN configuration. My current setup is as follows:

sys-netopenvpnothervpnfirefoxvm (with resolv.conf set to 1.1.1.1)

However, this configuration doesn’t work with the default nameservers set by Qubes, specifically:

nameserver 10.139.1.1
nameserver 10.139.1.2

I believe these addresses are automatically set by Qubes, and they are causing the issue.