OpenVPN and Internal DNS on ER7206 in Standalone Mode
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi TP-Link Community,
I’m using a TP-Link ER7206 (latest firmware) in Standalone Mode and need help with two things:
✅ 1. OpenVPN Access to LAN
I’ve configured OpenVPN, and remote clients can connect, but they can’t reach internal devices on the LAN (192.168.11.0/24).
I initially used the same subnet for the VPN IP Pool (192.168.11.0/24), which caused routing issues.
I’ve now changed the VPN pool to a non-overlapping subnet:
-
LAN:
192.168.11.0/24 -
VPN Pool:
10.8.0.0/24 -
“Allow clients to access the LAN” is enabled
-
I also added
route 192.168.11.0 255.255.255.0to the client config
But the VPN clients still can’t reach internal hosts.
✅ 2. Internal DNS for beast.dk
I host internal services under beast.dk. Externally, it resolves fine via public DNS.
Internally, I want beast.dk to resolve to its local IP (192.168.11.11). I’ve added a LAN DNS entry in the ER7206, and it works if clients use the router as DNS.
However, clients using external DNS (e.g. 1.1.1.1) bypass the override.
❓ Questions:
-
What else is needed to allow VPN clients to access the LAN?
-
Is there a way to enforce internal DNS or support NAT loopback in Standalone Mode?
-
Thanks in advance!
