I've currently tried firmwares 220.127.116.11 and 18.104.22.168 and neither of the two work properly with split dns
22.214.171.124 doesn't support Split DNS .
Split DNS was implemented in 126.96.36.199 which was pulled, so I can't even test that.
You can find the release notes here:
But the download itself doesn't exist. I've combed the internet and nothing.
I've set up Split DNS before with two RV042s and it works fine.
So this is my setup:
Subnet: 255.255.255.0 (this is intential)
Site to Site VPN:
Using RV220W's default IKE settings.
Split DNS Enabled
Primary DNS Server: 10.0.0.1
Primary Domain: dataprocomputers.com
(this is set up on the home network)
I'll skip the unnecessary stuff.
VPN connects fine. IKE is all good. Everything pings.
nslookup pdc01.dataprocomputers.com. 10.0.0.1
response is good
nslookup pdc01.dataprocomputers.com. 192.168.1.1
DNS Proxy enabled and disabled makes no difference.
Changing the RV220W's DHCP domain name to dataprocomputers.com doesn't matter
With Split DNS disabled 192.168.1.1 will respond with the WAN IP (because it's using the ISP). That's expected
With Split DNS enabled 192.168.1.1 never responds (no ip given)
Has anybody ever got Split DNS to work on 188.8.131.52 and higher? Can somebody share their 184.108.40.206 to see if this issue is on 220.127.116.11 and above?
These are all the different versions of RV220W firmware that I have. None of them are Beta; they are all GA releases.
Thanks. None of them worked. I checked my DNS server and it's not getting any requests from the RV220W. I guess I'm sending this thing back
I tried all firmwares, none of them work.
I set up my own linux server.
added one line to dnsmasq.conf
disabled the dhcp
pointed my dhcp clients to the linux server
and it worked.
Seriously, Cisco? Check your code. It's on your side.
I had encountered more strange issues using very similar structure as mentioned. I have established IPSec gateway to gateway VPN between RV220W (Firmware Version 18.104.22.168) a RV042 (Firmware Version: 22.214.171.124-tm). I use domain server (SBS2011). The Domain server is on side of RV042.
My statement is:
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 126.96.36.199. 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.
I know this is an old thread, but the issue reported by OP seems still to exist. The RV180 appears to have the same problem to according to this link https://supportforums.cisco.com/discussion/11661066/rv180-split-dns-not-working.
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:
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).