[132102] in North American Network Operators' Group
RE: Register.com DNS outages
daemon@ATHENA.MIT.EDU (Brandon Kim)
Sun Nov 14 14:28:41 2010
From: Brandon Kim <brandon.kim@brandontek.com>
To: <esanborn@tsd-inc.com>, <fw@deneb.enyo.de>
Date: Sun, 14 Nov 2010 14:28:36 -0500
In-Reply-To: <669085A52D23F14097D8DF74BAB4FCD4D7DE23@MAIL4.TSD-INC.com>
Cc: nanog group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Isn't using register.com considered outsourcing?=20
In fact=2C I'd probably feel better not outsourcing to a big shop who is su=
ch a big target.....a little security through obscurity doesn't hurt.... =
=3D)
> Subject: Re: Register.com DNS outages
> Date: Sun=2C 14 Nov 2010 14:03:27 -0500
> From: esanborn@tsd-inc.com
> To: fw@deneb.enyo.de=3B brandon.kim@brandontek.com
> CC: nanog@nanog.org
>=20
> Yes=2C however register.com does not allow their customers to list both t=
heir DNS servers and a customer's DNS server. End result is when the outage=
on their servers occurs you need to modify the config on their website so =
that it points back to your private DNS servers. Propagation delays are a p=
ain....
>=20
>=20
>=20
> ----- Original Message -----
> From: Florian Weimer <fw@deneb.enyo.de>
> To: Brandon Kim <brandon.kim@brandontek.com>
> Cc: nanog group <nanog@nanog.org>
> Sent: Sun Nov 14 13:48:55 2010
> Subject: Re: Register.com DNS outages
>=20
> * Brandon Kim:
>=20
> > Times like this=2C makes you curious what kind of infrastructure
> > register.com has? How does one protect against DDOS?
>=20
> You can outsource your DNS=2C but you better retain a server locally on
> your network=2C so that you suffer less from that particular shared
> toothbrush.
>=20
=
