Leaderboard

No, you cannot.. AirVPN's DDNS is designed so that a name you enter when forwarding a port resolves to the server a client is connected to, and so that this name can still be used to reach some client when the connection breaks and it happened to connect to another server. In other words, it only updates A/AAAA RRs, as DDNS is supposed to do, and only in relation to a VPN connection to AirVPN (which I believe will be blasphemous at work, going by the name pcwork). It is not possible to enter your own NS RRs. Be advised that the domain for DDNS names is airdns.org.

This is what I do: https://github.com/tool-maker/VPN_just_for_torrents/wiki/Running-OpenVPN-on-Windows-without-VPN-as-Default-Gateway Works for Wireguard too. You add routing table entries to put the original default gateway back in effect (using a provided script - copy and paste). Basically you have all public IP addresses routed outside the VPN. And then bind the torrent client to the VPN interface (or address) to have it use the VPN. In Windows, a program bound to the VPN interface will ignore routing table entries that are not for the VPN interface. So it sees the VPN as the only route. I have used this (I wrote the scripts there) for many years. Some people complain that this is too much reading/too technical/too much work. But you really just have to copy and paste a couple of .bat scripts for the routing. Also, a caveat. This really does rely on the torrent program binding properly to the VPN interface. From that page: "If you are using uTorrent, uTorrent (older releases at least) will ignore your instruction to bind the VPN and use the default gateway if the address you specify does not exist." Recent versions of qBittorrent seem to have become unreliable for this too. I use Transmission (transmission-daemon.exe). For safety, I use Windows firewall to block the torrent program from using the real interface. The method is to block out-going traffic for that program from IP ranges 192.168.0.0/16 (for IPv4) and 2000::/3 (for IPv6). This presumes that your router uses NAT for IPv4 (with the usual LAN private address range) but not for IPv6. You can start Windows Firewall by executing "wf.msc". Or find it in the start menu. Add the rules in "Outbound Rules". One for IPv4 and one for IPv6. The address goes in the "Scope" tab in "Local IP address". Check "Block the connection" in the "General" tab. The program path goes in the "Programs and Services" tab in "This program".