On Fri, Nov 27, 2009 at 01:52:31PM -0800, nate wrote:
>
> As others have mentioned using a proxy would work..
Proxy would be the best as it offers a lot of additional
features such as logging ability to see how much time
people are wasting at work. Squid setup as a transp
- "nate" wrote:
> James B. Byrne wrote:
>
> > Without debating the merits of such claims, how would one proceed
> to
> > block internal network access to specific domain names using
> CentOS?
>
> Also hosting the domains on your internal name server and pointing
> them to some internal addre
James B. Byrne wrote:
> Without debating the merits of such claims, how would one proceed to
> block internal network access to specific domain names using CentOS?
As others have mentioned using a proxy would work..
Other ways would be using iptables to block access to those
domain's name server
On Fri, Nov 27, 2009 at 12:32, Eero Volotinen wrote:
>
>>
>> Without debating the merits of such claims, how would one proceed to
>> block internal network access to specific domain names using CentOS?
>
> Using transparent proxy server is best way to block this kind of
> services. You can use squ
>
> Without debating the merits of such claims, how would one proceed to
> block internal network access to specific domain names using CentOS?
Using transparent proxy server is best way to block this kind of
services. You can use squid package to setup transparent proxy server.
--
Eero
__
We are considering whether or not to block internal access to social
networking and private entertainment web sites. This not a policy
decision as of yet, just an exploratory exercise.
Our gateways run CentOS-5.4 and use iptables to enforce firewall
rules. The information that we wish to determi
6 matches
Mail list logo
