Private IP address registered on Server DNS instead of the VPN assigned IP address
Remote users are connecting with Forticlient with an IPSec VPN configured in split tunnel. When I try to manage the computers by name, some of the computers cannot be found because on the Windows Server 2016 DNS the computers are getting registered not with the IP address assigned by the VPN configuration but with the private IP address of the user's home or location.
For example the IP address pool for the VPN goes from 10.10.50.20 to 10.10.50.200, at the user's home the user's router assigns 192.168.0.10 to the computer's nic and when it is connected with the VPN it also get the IP 10.10.50.46. When I check the A record in the DNS it have the IP address 192.168.0.10 and not 10.10.50.46. Even if I delete the A record and add it manually with 10.10.50.46, later on the system adds a new A record with the same computer name but with the 188.8.131.52 IP address. This is not happening with all computers but all of them are using the same IPSec VPN (split tunnel). For some of them the A record is properly created in the DNS with 10.10.50.XXX.
post edited by Edil - 2021/01/13 11:49:23