On Aug 7, 2014, at 11:28 AM, Philip Prindeville <philipp_s...@redfish-solutions.com> wrote:
> > Okay, I thought you were saying that the posted configuration would block the > entire CIDR range. It won’t. > > So they have a lot of VirtualHost definitions: a couple of comments on that. > > (1) putting that many domains on a single host is just begging for that host > to have a catastrophic failure (as opposed to putting that many domains on a > local (re)director which servers as a proxy, a la mod_proxy_html mode…) > > (2) it further means that if the host is compromised, then all the domains on > that host are compromised. > > (3) if that IP is being blocked for whatever reason, then that will motivate > the other users on that same host to either pressure eNom to flush that bad > actor ASAP, or they will move to another host… possibly with another provider. > > This is a reckless practice, and eNom will likely suffer consequences when > their users start to catch on to all of the ill effects of it, some of which > I listed above. > > No one wants their business reputation being sullied by association with > phishers, spammers, and hacked websites… > > -Philip And for what it’s worth, a lot of the ARIN contact information for eNom netblocks is incorrect and points to addresses which seem to go unread (or at least unresponded to). If that were my provider, I wouldn’t stand for it and I’d be out of there in a New York minute. -Philip
