<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebAccess v7.1.14-51822">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: Parler</title>
<style type="text/css">
body
{
font-family: Arial, Verdana, Sans-Serif ! important;
font-size: 12px;
padding: 5px 5px 5px 5px;
margin: 0px;
border-style: none;
background-color: #ffffff;
}
p, ul, li
{
margin-top: 0px;
margin-bottom: 0px;
}
</style>
</head>
<body>
<p>I think its more probable to say that AWS didn't even know about this. As far as I can see, epik is just another AWS customer who spun up an instance and is hosting dns on that instance. I doubt AWS is watching customers at a level that would detect this. But, I'm also sure that AWS has since caught wind of this and is watching closely. I just checked, and both listed servers are returning an A record for parler, although its bogus info (probably meant as a place holder with low TTL so no one caches an nxdomain).</p><p> </p><p> </p><p> </p><blockquote style="border-left: 2px solid #325FBA; padding-left: 5px;margin-left:5px;">><br />> $ dig parler.com ns<br />> ...<br />> parler.com. 300 IN NS ns4.epik.com.<br />> parler.com. 300 IN NS ns3.epik.com.<br />> ...<br />> ns3.epik.com. 108450 IN A 52.55.168.70<br /><br />It's quite possible that Amazon is playing this *entirely* by the book, and<br />the Parler crew haven't violated the terms of the nameserver hosting<br />agreement so Amazon hasn't cut that off.<br /><br type="_moz" /></blockquote>
</body>
</html>