I see your point, but I am not sure running the authoritative name servers for a site meets the popular definition of "hosting" them. Epik is currently denying that they are going to host Parler in a traditional sense, though they are the registrar for parler.com. since a couple of days ago.
Of course, Amazon could ding Epik for being Parler's registrar, but that would truly be a reach, since they aren't Parler's Web host. -- Hunter Fuller (they) Router Jockey VBH Annex B-5 +1 256 824 5331 Office of Information Technology The University of Alabama in Huntsville Network Engineering On Wed, Jan 13, 2021 at 5:42 PM Matt Corallo <na...@as397444.net> wrote: > > In case anyone thought Amazon was being particularly *careful* around their > enforcement of Parler's ban...this is from > today on parler's new host: > > $ dig parler.com ns > ... > parler.com. 300 IN NS ns4.epik.com. > parler.com. 300 IN NS ns3.epik.com. > ... > ns3.epik.com. 108450 IN A 52.55.168.70 > > $ whois 52.55.168.70 > ... > OrgName: Amazon Technologies Inc. > > and for the curious, ns4.epik.com is hosted by an Epik sub, but from a > cursory glance appears to be single-homed to > CDN77, which is vaguely surprising to me. > > Matt > > On 1/10/21 3:23 AM, William Herrin wrote: > > Anybody looking for a new customer opportunity? It seems Parler is in > > search of a new service provider. Vendors need only provide all the > > proprietary AWS APIs that Parler depends upon to function. > > > > https://www.washingtonpost.com/technology/2021/01/09/amazon-parler-suspension/ > > > > Regards, > > Bill HErrin > >
