<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi,<br>
<br>
This is just their DNS, parler.com itself returns to 0.0.0.0
now.<br>
<pre class="moz-signature" cols="72">-----
Alain Hebert <a class="moz-txt-link-abbreviated" href="mailto:ahebert@pubnix.net">ahebert@pubnix.net</a>
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 <a class="moz-txt-link-freetext" href="http://www.pubnix.net">http://www.pubnix.net</a> Fax: 514-990-9443
</pre>
<div class="moz-cite-prefix">On 1/14/21 12:02 AM, Valdis Klētnieks
wrote:<br>
</div>
<blockquote type="cite" cite="mid:137136.1610600523@turing-police">
<pre class="moz-quote-pre" wrap="">On Wed, 13 Jan 2021 18:41:55 -0500, Matt Corallo said:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
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.
</pre>
</blockquote>
<br>
</body>
</html>