Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

RV220W blocks the hosts file?

I have a somewhat odd problem - anything I put into my hosts file, will not go through the Cisco RV220W router.

This is part of the set up:

192.168.1.10 << RV220W

192.168.1. 15 << A client machine

192.168.1.99 << Internal DNS with forwarder to OpenDNS (208.67.222.222 & 208.67.220.220)

+ a laptop that's not on the internal network at all.

Now, the client machine and the laptop both have an entry in their hosts files:

174.156.12.81 insight.hello.com

From the laptop, I can both browse to insight.hello.com, and I can ping it in Xterm.

From the client machine (192.168.1.15) which is behind the Cisco Router/FW, I can ping insight.hello.com, but I can not browse to it.

This is especially strange since the ping goes through the Router every bit as much as the http traffic does, so why is the router giving me a DNS error on that, but the ping goes through just fine? Food for thought.

The hosts file is supposed to supercede any other information from anywhere, so it out to not be a problem for the router either. Yet, it obviously is.

I have tried to disable the internal DNS server as well as OpenDNS and just run the ISP's DNS servers, but no change - I still get that blue DNS error screen from the CIsco router.

Anyone got any ideas on why this is happening?

Above IP's & hosts are fictitious. Duh.

Edit:

I have found the solution to the problem.

The hosts file doesn't get blocked in a sense, but what happens is that if you have "Content Filtering" checked - even without any rules - the router can not verify that 174.156.12.81 is in fact insight.hello.com in this case, since it doesn't exist in the public DNS system.

So, I unchecked Content Filtering and now it works as it should.

Everyone's tags (2)
1 REPLY
Community Member

Re: RV220W blocks the hosts file?

I have found the solution to the problem.

The hosts file doesn't get blocked in a sense, but what happens is that if you have "Content Filtering" checked - even without any rules - the router can not verify that 174.156.12.81 is in fact insight.hello.com in this case, since it doesn't exist in the public DNS system.

So, I unchecked that and now it works as it should.

687
Views
0
Helpful
1
Replies
CreatePlease to create content