

Would be interesting to know which one that is. Though not 100% correct, you can read it as "we guarantee that in the next 60 minutes the IP address won't change". In this case, that duration is 60 minutes.

This is done to lower the load on DNS servers so that the same address is not requested over and over again but served from local storage for a time. If you resolve a name, it usually gets saved in a cache for the duration specified in a special DNS record.

Maybe i have to wait 1 hour as airvpn says in documentation for ipforwarding Now when I connect to vpn in my VPS, nomachine provides another ipaddress to connect to from my home pc, but I cannot connect yet. Though, this also means, if the VPS is not connected to AirVPN, you must use Hetzner's address again. If you use that address in NoMachine, you should be able to reach your server with an active VPN connection. Entering myname there for example will create a DDNS record of. On the port forwarding page, when you forward a port you can enter something in the DDNS field below it. The NoMachine connection comes in through the "new" IP address of the VPS, which will be the AirVPN exit IP. The VPN connection closes, so that traffic coming in to Hetzner's IP will be routed out on Hetzner's IP again. In both cases, NoMachine disconnects and cannot reconnect, unless one of two things happen: In the former case, if traffic from an AirVPN server comes back to you and you did not initiate the connection to the AirVPN server IP, your router drops the traffic – it doesn't know which of the devices in its network the traffic is meant for. This means that traffic coming in on Hetzner's IP will either be routed out through AirVPN's server or times out on the VPS entirely (because traffic must leave on the tunnel interface but is trying to get out on the physical one). When you connect to AirVPN with Eddie, all traffic is routed through the VPN. Oh, it's a remote desktop application, I see.
