📝 Correction | Cleanup DNS page #1841

Closed
opened 2020-04-19 18:56:03 +00:00 by nitrohorse · 4 comments
nitrohorse commented 2020-04-19 18:56:03 +00:00 (Migrated from github.com)

Description / Why I am making the suggestion

I'm thinking the DNS page could be cleaned up: it's quite busy with the lists. Below the table, we have these sections:


(table)

  • Terms
    • DoT
    • DoH
    • DNSCrypt
  • How to verify DNS is encrypted
    • DoH / DoT
    • dnscrypt-proxy
    • DNSSEC
    • QNAME Minimization
  • Software suggestions and Additional Information
    • Encrypted DNS clients for desktop
      • Firefox
    • Encrypted DNS clients for mobile
      • Android 9
      • DNSCloak
      • Nebulo
    • Local DNS servers
      • Stubby
      • Unbound
    • Network wide DNS servers
      • Pi-hole
      • NoTrack
    • Further Reading

I'm wondering about this outline instead for the DNS page:


(table)

  • Terms

    • DoT
    • DoH
    • DNSCrypt
  • (header) Encrypted DNS Client Recommendations for Desktop

    • (card) Firefox's built-in DoH resolver
    • (card) dnscrypt-proxy (for DoH, DNSCrypt, Anonymized DNSCrypt)
    • (card) Unbound (for DoT, DNSCrypt)
  • (header) Encrypted DNS Client Recommendations for Android

    • (card) Android 9's built-in DoT resolver
    • (card) Nebulo
  • (header) Encrypted DNS Client Recommendations for iOS

    • (card) DNSCloak

(list) Further Reading


And move the "How to verify DNS is encrypted" list to a new DNS related Wiki page.

Overall, I think we should shift some of this info to a new Wiki page and caridfy other info (related to https://github.com/privacytoolsIO/privacytools.io/issues/1466). I think the goal of this page is to share some providers that support encrypted DNS and then some client recommendations for users to then easily start using encrypted DNS if they want to. This cleanup would help refocus the page for this goal.

My connection with the software

Contributed to the original DNS page.

  • I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## Description / Why I am making the suggestion I'm thinking the [DNS page](https://www.privacytools.io/providers/dns/) could be cleaned up: it's quite busy with the lists. Below the [table](https://www.privacytools.io/providers/dns/#dns), we have these sections: --- (table) - Terms - DoT - DoH - DNSCrypt - How to verify DNS is encrypted - DoH / DoT - dnscrypt-proxy - DNSSEC - QNAME Minimization - Software suggestions and Additional Information - Encrypted DNS clients for desktop - Firefox - Encrypted DNS clients for mobile - Android 9 - DNSCloak - Nebulo - Local DNS servers - Stubby - Unbound - Network wide DNS servers - Pi-hole - NoTrack - Further Reading --- I'm wondering about this outline instead for the DNS page: --- (table) - Terms - DoT - DoH - DNSCrypt - (header) Encrypted DNS Client Recommendations for Desktop - (card) Firefox's built-in DoH resolver - (card) dnscrypt-proxy (for DoH, DNSCrypt, [Anonymized DNSCrypt](https://github.com/privacytoolsIO/privacytools.io/issues/1822)) - (card) Unbound (for DoT, DNSCrypt) - (header) Encrypted DNS Client Recommendations for Android - (card) Android 9's built-in DoT resolver - (card) Nebulo - (header) Encrypted DNS Client Recommendations for iOS - (card) DNSCloak (list) Further Reading --- And move the "How to verify DNS is encrypted" list to a new DNS related Wiki page. Overall, I think we should shift some of this info to a new [Wiki](https://wiki.privacytools.io/view/Main_Page) page and caridfy other info (related to https://github.com/privacytoolsIO/privacytools.io/issues/1466). I think the goal of this page is to share some providers that support encrypted DNS and then some client recommendations for users to then easily start using encrypted DNS if they want to. This cleanup would help refocus the page for this goal. ## My connection with the software Contributed to the original DNS page. - [x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
danarel commented 2020-04-21 23:11:48 +00:00 (Migrated from github.com)

While we're at it.

We need to remove SecureDNS as they are shutting down on April 30. https://securedns.eu/

We also need to add Vultr.com to AdGuard's hosting.

While we're at it. We need to remove SecureDNS as they are shutting down on April 30. https://securedns.eu/ We also need to add Vultr.com to AdGuard's hosting.
danarel commented 2020-04-23 06:12:34 +00:00 (Migrated from github.com)

Consider https://github.com/privacytoolsIO/privacytools.io/pull/1453 when redoing the site. Possibly for inclusion on the wiki instead.

Consider https://github.com/privacytoolsIO/privacytools.io/pull/1453 when redoing the site. Possibly for inclusion on the wiki instead.
blacklight447 commented 2020-05-05 07:37:23 +00:00 (Migrated from github.com)

@nitrohorse would you want to start a PR for this to show what you have in mind?

@nitrohorse would you want to start a PR for this to show what you have in mind?
nitrohorse commented 2020-05-05 07:58:16 +00:00 (Migrated from github.com)

@nitrohorse would you want to start a PR for this to show what you have in mind?

Sure thing 👍🏼

> @nitrohorse would you want to start a PR for this to show what you have in mind? Sure thing 👍🏼
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1841
No description provided.