Parler

Thu Jan 14 16:50:43 UTC 2021

Hi Matt,

That’s not how it would be done. There is an EPP status serverHold (or, if issued by the registrar, clientHold), which removes a domain from DNS. This is used after arbitration or court decisions and for cases of abuse. I doubt however that Verisign would suspend Parler’s domain.

Matthias Merkel
Staclar, Inc.

From: NANOG <nanog-bounces+matthias.merkel=staclar.com at nanog.org> On Behalf Of Matt Erculiani
Sent: Thursday, 14 January 2021 17:46
To: ahebert at pubnix.net
Cc: nanog at nanog.org list <nanog at nanog.org>
Subject: Re: Parler

Is there a remote possibility here that Verisign might say "yeah, we're gonna glue this domain down to 0.0.0.0 and not allow registration"? Is there any precedent for this? Would seem like a game of whack-a-mole that anyone would want to avoid.

Really that would seem like the only way to ratchet up the "internet death penalty" even further at this point, barring any major ISPs coming out and saying they'll block it from transiting their networks. Again, more whack-a-mole, and arguably a more serious precedent to set as Verisign isn't the only TLD registrar.

-Matt

On Thu, Jan 14, 2021 at 7:24 AM Alain Hebert <ahebert at pubnix.net<mailto:ahebert at pubnix.net>> wrote:
    Hi,

    This is just their DNS, parler.com<http://parler.com> itself returns to 0.0.0.0 now.

-----

Alain Hebert                                ahebert at pubnix.net<mailto:ahebert at pubnix.net>

PubNIX Inc.

50 boul. St-Charles

P.O. Box 26770     Beaconsfield, Quebec     H9W 6G7

Tel: 514-990-5911  http://www.pubnix.net    Fax: 514-990-9443
On 1/14/21 12:02 AM, Valdis Klētnieks wrote:

On Wed, 13 Jan 2021 18:41:55 -0500, Matt Corallo said:

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<http://parler.com> ns

...

parler.com<http://parler.com>.             300     IN      NS ns4.epik.com<http://ns4.epik.com>.

parler.com<http://parler.com>.             300     IN      NS ns3.epik.com<http://ns3.epik.com>.

...

ns3.epik.com<http://ns3.epik.com>.           108450  IN      A   52.55.168.70

It's quite possible that Amazon is playing this *entirely* by the book, and

the Parler crew haven't violated the terms of the nameserver hosting

agreement so Amazon hasn't cut that off.

--
Matt Erculiani
ERCUL-ARIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210114/49661a6f/attachment.html>