DNN Community Blog

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact community@dnnsoftware.com.

 


Using request filters in DotNetNuke to restrict website access

Have you ever had the need to blog a range of IP Addresses from accessing your website? Or perhaps, setup a website that is only accessible to a specific range of IP Addresses? DotNetNuke Request Filters are a great tool for getting such functionality configured, all configurable within your browser, without needing access to the settings in IIS.

Before configuring the request filters, I’ll throw out an example of why you might do this. If your website has a forum, or other community type interface, you have likely experienced spammers trying to take advantage of these features. Sometimes these spammers come from a specific IP Address, or even a specific range of ip addresses. If that is the case, you may want to turn off your website for those IP Addresses.

A word of warning, the instructions below are very powerful, if you aren’t careful, you could bring your website down. Read through the instructions before attempting to configure your website’s request filters.

Configuring your DotNetNuke website to be accessible from one IP Address

Here are the steps to configure request filtering for an IP Address, essentially making the website ONLY accessible to a person browsing from a computer using the defined IP address. All other addresses will redirect to DotNetNuke.com. (these instructions assume you are running on DotNetNuke 6+

  1. Login to your website with a Super User account (typically HOST).
  2. Navigate to the Host/Host Settings page.
  3. From there click on the Other Settings tab
  4. Check the Enable Request Filters checkbox image
  5. Click on Add New Rule image
  6. First we will configure the site to only be accessible from a specific IP Address (67.188.123.23). These settings configure all requests not from 67.188.123.23 to redirect to DotNetNuke.com image
  7. To SAVE your new rule, click on the disk icon to the left of the Server Variable field.
  8. If you access the site from the IP Address defined above, the site would function as normal.
  9. If you access the site from a different IP Address than the one defined above, you would be redirected to DotNetNuke.com

Configuring your DotNetNuke website to NOT be accessible from a range of IP Addresses

  1. Login to your website with a Super User account (typically HOST).
  2. Navigate to the Host/Host Settings page.
  3. From there click on the Other Settings tab
  4. Check the Enable Request Filters checkbox image
  5. Click on Add New Rule image
  6. First we will configure the site to NOT be accessible from a specific IP Address range (67.188.1.1-254). These settings configure all requests from this range to redirect to DotNetNuke.com, all other requests would access the site as normal. image
  7. To SAVE your new rule, click on the disk icon to the left of the Server Variable field.
  8. If you access the site from the IP Address in the range defined above, the site would redirect.
  9. If you access the site from a different IP Address than the range defined above, the site would function as normal.

If you are having trouble generating the proper regular expression for a Range of IP Addresses you can check out this page on Google Answers.

If you happen to screw up a rule, and make your site inaccessible, if you can access the file system (either via the server, or FTP) you can find the rules defined in the dotnetnuke.config file in the root of your website.

Be careful if you play around with request filters! They can be very powerful tools.

Comments

Chee Chiu Ng
Hi, is it possible to restrict access for the login page only?
Chee Chiu Ng Wednesday, March 12, 2014 10:46 PM (link)
cathal connolly
@Chee you can use IP filtering to block admin/host loging's for certain addresses http://www.dnnsoftware.com/help#Documentation/Using_the_Control_Panel/Host_Console/Host_Settings/Advanced_Settings/Login_IP_Filters/Login_IP_Filters.html?Highlight=ip filter
cathal connolly Thursday, March 13, 2014 12:04 PM (link)
Chris Hammond
Nice url wrap there...
Chris Hammond Thursday, March 13, 2014 12:05 PM (link)

Comment Form

Only registered users may post comments.

NewsArchives


Aderson Oliveira (4)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (13)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (7)
Bill Walker (36)
Bob Kruger (5)
Brian Dukes (1)
Brice Snow (1)
Bruce Chapman (9)
Bryan Andrews (1)
cathal connolly (52)
Charles Nurse (157)
Chris Hammond (197)
Chris Paterra (55)
Clinton Patterson (26)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (34)
Dave Buckner (2)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (67)
Geoff Barlow (2)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (236)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (1)
Keivan Beigi (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (1)
Michael Washington (202)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Patrick Santry (3)
Peter Donker (50)
Philip Beadle (135)
Philipp Becker (2)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (11)
Scott Wilkinson (1)
Scott Willhite (97)
Sebastian Leupold (78)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Timo Breumelhof (24)
Torsten Weggen (1)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (36)
Will Strohl (145)
William Severance (5)

Copyright 2014 by DNN Corp Terms of Use Privacy
Request
a Demo
See Evoq Live
Latest Blog
How to Make Advocate Marketing Work for You
Read It
Watch the Replay
Top 5 Reasons to Consider a Branded Online Community
Watch