1
Virtual private networks / Re: Can't join domain over OpenVPN connection
« on: June 15, 2024, 05:18:58 am »
OK, here's how I resolved it for anyone attempting something of this nature.
I configured a VPN connection on our local LAN DNS server to the remote LAN, then created a forward lookup zone in DNS for the remote domain name. After creating it, I went into the Name Server (NS) entry which was currently set to the local LAN DC/DNS server and changed it to the remote LAN DNS server's FQDN. When adding its IP address in the entry, it successfully resolved to it.
After doing this, I was able to join the new server to the remote domain. I restarted it, but it took quite a while to login, probably trying to resolve to the remote DC without the VPN. Then I tried promoting it to DC once the VPN was up but had resolution problems again, this time with the OpenVPN client, It wouldn’t connect. I tested the remote A record it was configured to use with NSLOOKUP, it wouldn’t resolve. To fix this, I simply went into the VPN NIC properties on the new server and set the DNS server client settings to 8.8.8.8. After this it resolved successfully, and I was able to promote the new server to DC.
I configured a VPN connection on our local LAN DNS server to the remote LAN, then created a forward lookup zone in DNS for the remote domain name. After creating it, I went into the Name Server (NS) entry which was currently set to the local LAN DC/DNS server and changed it to the remote LAN DNS server's FQDN. When adding its IP address in the entry, it successfully resolved to it.
After doing this, I was able to join the new server to the remote domain. I restarted it, but it took quite a while to login, probably trying to resolve to the remote DC without the VPN. Then I tried promoting it to DC once the VPN was up but had resolution problems again, this time with the OpenVPN client, It wouldn’t connect. I tested the remote A record it was configured to use with NSLOOKUP, it wouldn’t resolve. To fix this, I simply went into the VPN NIC properties on the new server and set the DNS server client settings to 8.8.8.8. After this it resolved successfully, and I was able to promote the new server to DC.