DNS: add Snopyta #1339

Merged
Mikaela merged 2 commits from snopyta-dns into master 2019-09-27 06:56:31 +00:00
1 changed files with 39 additions and 2 deletions

View File

@ -150,7 +150,7 @@
<a href="https://www.datacenterlight.ch/">Data Center Light</a>,
</span>
<span class="no-text-wrap">
<a href="https://www.hetzner.com/">Hetzner Online GmbH</a>,
<a href="https://www.hetzner.com/">Hetzner Online GmbH</a>
</span>
</td>
</tr>
@ -458,7 +458,44 @@
<td>?</td>
<td>
<span class="no-text-wrap">
<a href="https://www.digitalocean.com/">DigitalOcean, Inc.</a>,
<a href="https://www.digitalocean.com/">DigitalOcean, Inc.</a>
</span>
Mikaela commented 2019-09-23 14:32:21 +00:00 (Migrated from github.com)
Review
            <a href="https://www.hetzner.com/">Hetzner Online GmbH</a>

I guess I should remove this comma and there are a lot of excess commas with a closer look. And I thought I force pushed the privacy policy away?

```suggestion <a href="https://www.hetzner.com/">Hetzner Online GmbH</a> ``` I guess I should remove this comma and there are a lot of excess commas with a closer look. And I thought I force pushed the privacy policy away?
</td>
</tr>
<tr>
<td data-value="Snopyta">
<a href="https://snopyta.org/service/dns/index.html">Snopyta</a>
</td>
<td>
<span class="no-text-wrap">
<span class="flag-icon flag-icon-fi"></span>
Finland
</span>
</td>
<td>
<a data-toggle="tooltip" data-placement="bottom" data-original-title="https://snopyta.org/privacy_policy/" href="https://snopyta.org/privacy_policy/">
<img alt="WWW" src="/assets/img/layout/www.png" width="35" height="35">
</a>
</td>
<td>
<a data-toggle="tooltip" data-placement="bottom" data-original-title='Part of LibreHosters, "a network of cooperation and solidarity that uses free software to encourage decentralisation through federation and distributed platforms."' href="https://libreho.st/">
Informal collective
Mikaela commented 2019-09-23 14:27:39 +00:00 (Migrated from github.com)
Review

I wonder if I should call it as Snopyta DNS?

I wonder if I should call it as Snopyta DNS?
nitrohorse commented 2019-09-24 03:49:41 +00:00 (Migrated from github.com)
Review

For consistency if we do, then I think we should update these also, yeah?

  • AdGuard DNS
  • NixNet DNS

I think it's also fine how it is without "DNS."

For consistency if we do, then I think we should update these also, yeah? - AdGuard DNS - NixNet DNS I think it's also fine how it is without "DNS."
</a>
</td>
<td>No</td>
<td>DoH, DoT</td>
<td>Yes</td>
<td>Yes</td>
<td>
<span class="no-text-wrap">
No
</span>
</td>
<td>?</td>
<td>
<span class="no-text-wrap">
Mikaela commented 2019-09-23 14:28:05 +00:00 (Migrated from github.com)
Review

I just copy-pasted this and wonder if LibreHosters should be a type?

I just copy-pasted this and wonder if LibreHosters should be a type?
nitrohorse commented 2019-09-24 03:50:50 +00:00 (Migrated from github.com)
Review

I'm not sure, maybe? Leaving the type as "informal collective" makes it easy to add future DNS that are under a different collective I guess.

I'm not sure, maybe? Leaving the type as "informal collective" makes it easy to add future DNS that are under a different collective I guess.
Mikaela commented 2019-09-24 09:22:53 +00:00 (Migrated from github.com)
Review

Ok, I guess I will let it be.

Ok, I guess I will let it be.
<a href="https://www.hetzner.com/">Hetzner Online GmbH</a>
</span>
</td>
</tr>
Mikaela commented 2019-09-23 14:30:00 +00:00 (Migrated from github.com)
Review

There are no IP addresses nor any queries logged by default. In order to prevent abuse we monitor traffic volume which may result in temporary enabling logs to block IP addresses. These logs are deleted immediately after action has been taken and are kept for a maximum of 24 hours.

but I think similar scenarios were marked as not logging. I wonder if the title should have a warning "on normal operation" or similar (as that is in our requirements)?

> There are no IP addresses nor any queries logged by default. In order to prevent abuse we monitor traffic volume which may result in temporary enabling logs to block IP addresses. These logs are deleted immediately after action has been taken and are kept for a maximum of 24 hours. but I think similar scenarios were marked as not logging. I wonder if the title should have a warning "on normal operation" or similar (as that is in our requirements)?
nitrohorse commented 2019-09-24 03:51:42 +00:00 (Migrated from github.com)
Review

I think if you look at Quad9, it's the same situation: we state "Some" with a tooltip regarding this type of scenario.

I think if you look at Quad9, it's the same situation: we state "Some" with a tooltip regarding this type of scenario.
Mikaela commented 2019-09-24 09:23:46 +00:00 (Migrated from github.com)
Review

I need to check later, but I think Nixnet or Lelux or similar had this.

I need to check later, but I think Nixnet or Lelux or similar had this.
Perflyst commented 2019-09-24 10:42:30 +00:00 (Migrated from github.com)
Review

Everyone needs to enable logging if there is abuse and if the provider writes you an email because your server was part of a DNS reflection DDoS. If I claim I will never log than this is a lie and I also would hurt the full DNS network.

Everyone needs to enable logging if there is abuse and if the provider writes you an email because your server was part of a DNS reflection DDoS. If I claim I will never log than this is a lie and I also would hurt the full DNS network.
Perflyst commented 2019-09-24 10:43:55 +00:00 (Migrated from github.com)
Review

But ok, we can do it like this: I do never log any DNS queries.
I still can use tcpdump or similar to get the information needed to stop the abuse. Is this logging?

But ok, we can do it like this: I do never log any DNS queries. I still can use tcpdump or similar to get the information needed to stop the abuse. Is this logging?