Description
You can configure Access Server to preserve VPN client IP addresses in DNS queries instead of using network address translation (NAT) to replace them with the Access Server IP address.
Preserving client IP addresses helps you monitor and troubleshoot DNS traffic. For example, if a threat detection system identifies a malicious DNS query, you can determine which VPN client sent it.
Important: Access Server 3.1.0 introduced Domain Routing, which uses a DNS proxy to forward client DNS queries to upstream DNS servers. When DNS queries pass through this proxy, the upstream DNS server doesn't see the original VPN client IP address.
To preserve a client IP address, ensure the the affected users don't have Domain Routing rules configured directly or inherited from their group or the global configuration.
Configure DNS Traffic Routing
To preserve VPN client IP addresses in DNS queries, configure subnet routing override for your DNS servers.
- Sign in to the Admin Web UI.
- Navigate to Access Controls → Global Access Rules → Global Subnet Routing Overrides.
- Select Add new subnet routing override, and enter the IP address of your DNS server.
- Repeat the previous step for each additional DNS server.
- Select Save, then select Restart to apply the changes.
- Ensure that your DNS servers or their network gateways have a route back to the VPN client subnet through Access Server.
Verify DNS Traffic
Confirm that your DNS server receives queries with the original VPN client IP address rather than the Access Server IP address.
If you can’t configure return routing for DNS traffic, you can run a packet capture, tcpdump, on Access Server to identify the original source IP address.
Capture VPN traffic on the VPN tunnel and inspect the source IP address before NAT translates the traffic as it leaves Access Server.
Need help?
If you have questions, submit a support ticket.
Comments
0 comments
Please sign in to leave a comment.