Article

phxazcraig's picture
article
Reads:

3961

Score:
0
0
 
Comments:

0

Blocking Sub-Domain Access in BorderManager

Author Info

26 September 2007 - 3:02am
Submitted by: phxazcraig

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Problem

A Forum reader recently asked:

"I been observing that sub-domains can be accessed when the main domain is blocked. For example, content.movies.myspace.com can be access when www.myspace.com is in the ACL list as blocked. Can wildcards be used like when filtering file extensions? Will *.myspace.com work as a filter?"

And here's the response from Craig Johnson ...

Solution

Yes, wildcards can, and should, be used in access rules. It is typical to have entries like these:

*.domain.com
*.domain.com/*

(These would both be in the same rule, though you would think the second rule would cover all bases).

Note that you can't use a https rule - it will be ignored. You can, however, use a port 443 rule blocking a domain, and some people here have reported success with a rule like www.domain.com:443/*.


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

© 2013 Novell