this is not the right way to block access to a site as i can setup my own dns or use foreign nameservers
but what is the best method? blocking ip traffic to the site can also mean to block legitimate traffic to a shared hosting server!? cheers oliver On Feb 17, 2009, at 4:57 PM, "Xaver Aerni" <<mailto:xae...@pop.ch>xae...@pop.ch<mailto:xae...@pop.ch>> wrote: When the ISP block it only by DNS Filtering??? I think to block 1 side is a DNS Filtering the easyest and fastest way. Greetings Xaver ----- Original Message ----- From: Yann Gauteron<mailto:ygaute...@gmail.com> To: <mailto:swi...@swinog.ch> <mailto:swi...@swinog.ch> swi...@swinog.ch<mailto:swi...@swinog.ch> Sent: Tuesday, February 17, 2009 4:50 PM Subject: Re: [swinog] Post from Canton de Vaud You're assuming that the biggest ISPs will apply the filtering at the entrance of their network, which is not necesseraly true. They can also decide to filter closer to their access equipments. This would mean that peerings with other ISPs or BGP-tiered enterprises would be unfiltered. Depending where the filtering is applied, professional access could also be prevented to be filtered. ________________________________ _______________________________________________ swinog mailing list <mailto:swinog@lists.swinog.ch>swinog@lists.swinog.ch<mailto:swinog@lists.swinog.ch> http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog _______________________________________________ swinog mailing list <mailto:swinog@lists.swinog.ch>swinog@lists.swinog.ch<mailto:swinog@lists.swinog.ch> <http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog>http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
