Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Block Traffic from a Specific Domain
Is there a way I can block all traffic from a specific domain?
Currently i have a Cisco RV042G Gigabit Dual WAN VPN Router as my gateway.
Currently i have a Cisco RV042G Gigabit Dual WAN VPN Router as my gateway.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Please explain, what type of traffic are you looking to block? To which application/service?
The restriction might be on the application/service layer.
You can block access if you know their IP ranges. From discussion https://supportforums.cisco.com/thread/2153386 image of firewall rules
https://supportforums.cisco.com/servlet/JiveServlet/download/3655134-129391/firewall4.PNG
You would add a deny on the wan for those IP ranges.
Depending on service/application, it may have a way to deny access based on domain referenced in the reverse DNS.
The restriction might be on the application/service layer.
You can block access if you know their IP ranges. From discussion https://supportforums.cisco.com/thread/2153386 image of firewall rules
https://supportforums.cisco.com/servlet/JiveServlet/download/3655134-129391/firewall4.PNG
You would add a deny on the wan for those IP ranges.
Depending on service/application, it may have a way to deny access based on domain referenced in the reverse DNS.
Firewall->Content Filter->Forbidden Domains
use the NetBIOS name (eg instead of blocking www.doamin.com, block domain.com)
https://supportforums.cisco.com/thread/2023056
use the NetBIOS name (eg instead of blocking www.doamin.com, block domain.com)
https://supportforums.cisco.com/thread/2023056
The asker seems to want external resources from a specific doman restricted from accessing their resources rather than preventing local users from accessing an external resource.
Arnold..... There is a bigger problem if traffic traverses a network without invitation from inside. If you have unsolicited traffic in filtering your network, there is a guarantee that there is a worm on one of the workstations or someone had granted explicit access to the domain unknowingly.
I think the author needs to clarify his request at this point
I think the author needs to clarify his request at this point
I agree that one could go that the issue is responses coming in from a domain and the asker ones to block it. Your DNS adjustment will prevent access from inside to that domain so no response will be coming back.
The other (my understanding of the question as asked) deals with the asker having an app/service/etc. that needs to be restricted from receiving requests based on a domain name.
Domains do not really generate traffic, but the point is you could restrict on several application based on the domain that is identified by resolving the IP.
Not all IPS resolve to a name, so knowing the range of IPs from which you want access blocked is imperative.
The more rules you add, the worse the performance of your router will become since it has to evaluate everyrule in the order.
you would usually define deny rules before allow ones.
1 deny from_networks_I_do_not_lik
allow established (meaning a request from the LAN went out and this matches a response coming back)
2 deny IP1_range to HTTP
3 allow everyoneelse to http
Ordering the rules based on most use is a more efficient use of resources.
Depending on how involved you want to get, you could look at setting up an IPS/IDS using a linux box with two network interfaces with iptables and snort.
It could be in transparent mode where it sits between the router and the LAN.
http://www.fwbuilder.org/ might help you in crafting rules.
http://www.snort.org/
The other (my understanding of the question as asked) deals with the asker having an app/service/etc. that needs to be restricted from receiving requests based on a domain name.
Domains do not really generate traffic, but the point is you could restrict on several application based on the domain that is identified by resolving the IP.
Not all IPS resolve to a name, so knowing the range of IPs from which you want access blocked is imperative.
The more rules you add, the worse the performance of your router will become since it has to evaluate everyrule in the order.
you would usually define deny rules before allow ones.
1 deny from_networks_I_do_not_lik
allow established (meaning a request from the LAN went out and this matches a response coming back)
2 deny IP1_range to HTTP
3 allow everyoneelse to http
Ordering the rules based on most use is a more efficient use of resources.
Depending on how involved you want to get, you could look at setting up an IPS/IDS using a linux box with two network interfaces with iptables and snort.
It could be in transparent mode where it sits between the router and the LAN.
http://www.fwbuilder.org/ might help you in crafting rules.
http://www.snort.org/
Premium Content
You need an Expert Office subscription to comment.Start Free Trial