I had encountered more strange issues using very similar structure as mentioned. I have established IPSec gateway to gateway VPN between RV220W (Firmware Version 22.214.171.124) a RV042 (Firmware Version: 126.96.36.199-tm). I use domain server (SBS2011). The Domain server is on side of RV042.
My statement is:
•1. It is not possible to get through VPN all IPs (some PCs are invisible) on side of RV042, I tried set up split DNS, it does not work. I had Router WRVS4400N before and everything worked OK.
•2. If I update RV042 to the latest firmware (1.3.13.02-tm), it is impossible register some PCs on side of RV220W to the domain.
I would expect better work from leading company like CISCO thinks.
In search for a solution to this I replaced our internal DNS IP, which is accessible through the VPN tunnel, with a publicly available DNS IP such as 188.8.131.52. After that requests to the Split DNS zone configured in the VPN policy are forwarded to the correct server by the DNS proxy. So the problem seems to be that the proxy is not forwarding the Split DNS request to the correct interface which cause the request to time out.
Our scenarios is that the RV220W is used in a small office with only client machines. When there is a need to access servers at HQ, I would like the DNS query to be routed to our internal DNS servers based upon our domain name. For all other DNS lookups the DNS of the ISP should be used to avoid unnecessary traffic over the IPSec tunnel.
The configuration is:
IPv4 LAN (Local Network):
DHCP:Primary DNS Server = RV220W's LAN address
DNS Proxy: enabled
Split DNS: enabled
Advanced VPN Setup:VPN Policy Configuration
Domain Name Server 1: IP of our internal DNS server on the other side of the IPSec tunnel
Domain Name 1: Our domain name i.e. in our internal DNS server we have all hosts in our domain
Besides tunneling all traffic, does anyone know about a way to direct all DNS queries for our domain through the tunnel to our internal and protected DNS servers, but use the ISP's DNS servers for all other look-ups? Btw, we do not have overlapping sub-nets (bad idea in the first place).
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...