I recently installed OpenVPN in AWS EC2. I managed to get everything working, but there seems to be a glaring problem with all my client's DNS lookups routed through the VPN, even though I have a suffix specified. If I use these settings: [img]http://i.imgur.com/t1nTmvY.png[/img] then a route trace to yahoo.com yields these correct results: [code]>tracert yahoo.com Tracing route to yahoo.com [206.190.36.45] over a maximum of 30 hops: 1 1 ms 3 ms 1 ms 192.168.0.254 2 19 ms 18 ms 12 ms ...[/code] In the trace, 192.168.0.254 is my home router. Note that I also have the "Default domain suffix" option specified, because I want DNS lookups for that suffix to be processed through the VPN instead of through my home network's DNS. Now, if I change the aforementioned DNS setting like so: [img]http://i.imgur.com/aUKYLXH.png[/img] and perform the same route trace, I get the following result: [code]>tracert yahoo.com Tracing route to yahoo.com [98.139.183.24] over a maximum of 30 hops: 1 1 ms 2 ms 1 ms ip-192-168-0-254.us-west-2.compute.internal [192.168.0.254] 2 17 ms 18 ms 9 ms ...[/code] I was expecting DNS lookups to suffixes other than the one configured in OpenVPN to be routed through my home router; instead, they are routed through OpenVPN. So far, I have been unsuccessful in finding a configuration that gives me the desired outcome. Additionally, I am unsure if Internet traffic is actually still going through my home router, or if it is all being redirected through the VPN even though the setting says it shouldn't; I am not sure how to test this theory, however. I'd love some help with this issue. Am I misunderstanding the way something works? I simply want all traffic not destined for 10.0.0.0/16 and all DNS requests other than *.corp.*.com to go through my home router.

Client routing Internet traffic through VPN unexpectedly

VisualCSharp

I recently installed OpenVPN in AWS EC2. I managed to get everything working, but there seems to be a glaring problem with all my client's DNS lookups routed through the VPN, even though I have a suffix specified. If I use these settings:

then a route trace to yahoo.com yields these correct results:

>tracert yahoo.com
Tracing route to yahoo.com [206.190.36.45]
over a maximum of 30 hops:

  1     1 ms     3 ms     1 ms  192.168.0.254
  2    19 ms    18 ms    12 ms  ...

In the trace, 192.168.0.254 is my home router. Note that I also have the "Default domain suffix" option specified, because I want DNS lookups for that suffix to be processed through the VPN instead of through my home network's DNS.

Now, if I change the aforementioned DNS setting like so:

and perform the same route trace, I get the following result:

>tracert yahoo.com
Tracing route to yahoo.com [98.139.183.24]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  ip-192-168-0-254.us-west-2.compute.internal [192.168.0.254]
  2    17 ms    18 ms     9 ms  ...

I was expecting DNS lookups to suffixes other than the one configured in OpenVPN to be routed through my home router; instead, they are routed through OpenVPN. So far, I have been unsuccessful in finding a configuration that gives me the desired outcome. Additionally, I am unsure if Internet traffic is actually still going through my home router, or if it is all being redirected through the VPN even though the setting says it shouldn't; I am not sure how to test this theory, however.

I'd love some help with this issue. Am I misunderstanding the way something works? I simply want all traffic not destined for 10.0.0.0/16 and all DNS requests other than *.corp.*.com to go through my home router.