[LAC-TF] CloudFlare Automatic IPv6 Gateway
Alejandro Acosta
alejandroacostaalamo at gmail.com
Tue Feb 7 14:00:27 BRST 2012
Hola,
Hoy utilizando cloudflare me acordé de esta vieja discusión en la lista:
On 9/29/11, Fernando Gont <fernando at gont.com.ar> wrote:
> Hola, Alejandro,
>
> On 09/28/2011 06:13 PM, Alejandro Acosta wrote:
>> Acabo de configurar un dominio..., vamos a ver como me va.
>> Indiscutiblemente es demasiado sencillo, es con un wizard que te lleva
>> paso a paso (son 3 o 4 pasos). Lo unico que veo "fastidioso" es que hay
>> que cambiar los DNS autoritativos para el dominio y moverlos a los DNS
>> de cloudflare.com <http://cloudflare.com>
>
> Hay algun motivo particular por el cual se requiere esto?
Cloudflare colocó la razón por la que piden mover los DNS
autoritativos a sus NSs:
-- cut here --
Why do my DNS settings have to be changed
CloudFlare does not require you to buy hardware, install software or
change any code to get protection. Instead, you deploy CloudFlare by
changing the current authoritative name servers for your domain. This
allows us to route potentially malicious traffic to your site through
our advanced filtering network and stop attackers before they reach
your server as well as accelerate your content. This means that
CloudFlare now becomes your DNS provider. You keep your current
hosting provider and registrar.
-- cut here --
¿Que opinan de la parte donde indican: "This allows us to route
potentially malicious traffic to your site through our advanced
filtering network and stop attackers before they reach your server"?
Saludos,
>
> Saludos,
> --
> Fernando Gont
> e-mail: fernando at gont.com.ar || fgont at acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>
>
>
>
More information about the LACTF
mailing list