dns: mention Unbound & ctrl.blog on Actually secure DNS over TLS in Unbound #1219

2019-08-25T10:00:59Z

Mikaela commented

2019-08-25 10:00:59 +00:00

(Migrated from github.com)

Description

Resolves: partially https://github.com/privacytoolsIO/privacytools.io/issues/1055

Check List

I have read and understand the contributing guidelines.
I have listed the source code.
This project is free/libre software.
This project has an associated discussion.

Netlify preview for the mainly edited page: https://deploy-preview-1219--privacytools-io.netlify.com/providers/dns/#icanndns
Code Repository (if applicable): https://github.com/NLnetLabs/unbound

## Description Resolves: partially https://github.com/privacytoolsIO/privacytools.io/issues/1055 #### Check List  - [x] I have read and understand [the contributing guidelines](https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md). - [x] I have [listed the source code](https://github.com/privacytoolsIO/privacytools.io/blob/master/source_code.md). - [x] This project is [free/libre software](https://www.wikipedia.org/wiki/Free_software). - [x] This project has an [associated discussion](https://github.com/privacytoolsIO/privacytools.io/issues). * Netlify preview for the mainly edited page: https://deploy-preview-1219--privacytools-io.netlify.com/providers/dns/#icanndns * Code Repository (if applicable): https://github.com/NLnetLabs/unbound

jonah reviewed

2019-08-25 10:00:59 +00:00

dawidpotocki (Migrated from github.com) reviewed

2019-08-25 10:00:59 +00:00

Mikaela (Migrated from github.com) reviewed

2019-08-25 10:01:53 +00:00

_includes/sections/dns.html

Mikaela (Migrated from github.com) commented

2019-08-25 10:01:52 +00:00

I kind of feel dirty for pull requesting my own config file / project, even if it has been talked previously and had positive reception.

netlify[bot] commented

2019-08-25 10:02:30 +00:00

(Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit d08283c1b6

https://deploy-preview-1219--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit d08283c1b63d090cf14d42ac08c533885102b160 https://deploy-preview-1219--privacytools-io.netlify.com

nitrohorse (Migrated from github.com) reviewed

2019-08-25 18:39:21 +00:00

nitrohorse (Migrated from github.com) left a comment

Small suggestions but LGTM

_includes/sections/dns.html

nitrohorse (Migrated from github.com) commented

2019-08-25 18:37:33 +00:00

I’m not sure if stating the version numbers is really beneficial for users?

nitrohorse (Migrated from github.com) commented

2019-08-25 18:38:59 +00:00

I think we could just break this into separate sentences:

...this list. Always read...

I think we could just break this into separate sentences: > ...this list. Always read...

Mikaela (Migrated from github.com) reviewed

2019-08-25 20:47:24 +00:00

_includes/sections/dns.html

Mikaela (Migrated from github.com) commented

2019-08-25 20:47:23 +00:00

In my opinion yes, because Ubuntu 18.04 LTS has Unbound 1.6.7-1ubuntu2.1 and Debian 9 (oldstable) has 1.6.0-3+deb9u2.

Ubuntu 18.04 is the latest LTS release, the next one will be 19.04 and I think a general rule of thumb for production systems is to not update to a new Debian until the first point release and Debian 10.1 is currently scheduled for 2019-09-07 as far as I am aware.

Debian 10 would have 1.9.0-2 which is higher than the minimum 1.7.3.

I don't want to hold Unbound back due to the two distribution versions having old versions and I don't want to add and have to manage warnings, so I think having the version number listed is the least worst solution and any advanced user setting it up should notice the version number mismatch while troubleshooting weird errors.

Also those two distributions have older version on dnscrypt-proxy, which is why I wrote https://mikaela.info/blog/english/2018/10/21/dnscrypt-proxy-quick-dirty-debian.html .

To complicate the matters with dnscrypt-proxy further (and sidetrack), as the v2 is written in Go and Debian hasn't yet figured out gomodules (AFAIK), Debian 11 (testing) is stuck with 2.0.19+ds1-2+b11 while the current version upstream is 2.0.25.

In my opinion yes, because Ubuntu 18.04 LTS has Unbound 1.6.7-1ubuntu2.1 and Debian 9 (oldstable) has 1.6.0-3+deb9u2. Ubuntu 18.04 is the latest LTS release, the next one will be 19.04 and I think a general rule of thumb for production systems is to not update to a new Debian until the first point release and Debian 10.1 is currently scheduled for 2019-09-07 as far as I am aware. Debian 10 would have 1.9.0-2 which is higher than the minimum 1.7.3. I don't want to hold Unbound back due to the two distribution versions having old versions and I don't want to add and have to manage warnings, so I think having the version number listed is the least worst solution and any advanced user setting it up should notice the version number mismatch while troubleshooting weird errors. Also those two distributions have older version on dnscrypt-proxy, which is why I wrote https://mikaela.info/blog/english/2018/10/21/dnscrypt-proxy-quick-dirty-debian.html . To complicate the matters with dnscrypt-proxy further (and sidetrack), as the v2 is written in Go and Debian hasn't yet figured out gomodules (AFAIK), Debian 11 (testing) is stuck with `2.0.19+ds1-2+b11` while the current version upstream is 2.0.25.

Mikaela (Migrated from github.com) reviewed

2019-08-25 20:47:58 +00:00

_includes/sections/dns.html

Mikaela (Migrated from github.com) commented

2019-08-25 20:47:58 +00:00

Will do

nitrohorse (Migrated from github.com) reviewed

2019-08-25 20:50:04 +00:00

_includes/sections/dns.html

nitrohorse (Migrated from github.com) commented

2019-08-25 20:50:04 +00:00

Wow TIL! Thanks for explaining @Mikaela 👍 Yes, I agree, we should keep the version number then 😄

Wow TIL! Thanks for explaining @Mikaela :+1: Yes, I agree, we should keep the version number then :smile:

nitrohorse (Migrated from github.com) reviewed

2019-08-25 20:50:59 +00:00

_includes/sections/dns.html

nitrohorse (Migrated from github.com) commented

2019-08-25 20:50:58 +00:00

Would it make sense to have a direct copy in this repo then? It won't reflect easily changes you adapt though which could be useful for users.

Mikaela (Migrated from github.com) reviewed

2019-08-25 20:58:20 +00:00

_includes/sections/dns.html

Mikaela (Migrated from github.com) commented

2019-08-25 20:58:20 +00:00

I am not sure that would be a good idea either and it would duplicate the amount of work for me or possibly other users.

What would you say @JonahAragon ?

I am not sure that would be a good idea either and it would duplicate the amount of work for me or possibly other users. What would you say @JonahAragon ?