[arch-dev-public] Dropping dingo from [community]
Hi All, I have removed dingo the Google DNS-over-HTTPS client from [community]. The upstream is inactive for years and supports Google only. I would recommend dns-over-https [1] instead which has support for multiple protocols and is still actively maintained. Note that Google announced [2] yesterday that they recommend to use the newer IETF protocol (at a new endpoint), which is also the protocol of all other major DoH providers (CloudFlare, Quad9, etc). [1] https://www.archlinux.org/packages/community/x86_64/dns-over-https/ [2] https://security.googleblog.com/2019/06/google-public-dns-over-https-doh.htm... -- Regards, Felix Yan
On Thu, Jun 27, 2019 at 03:43:37PM +0800, Public mailing list for Arch Linux development wrote:
Hi All,
I have removed dingo the Google DNS-over-HTTPS client from [community]. The upstream is inactive for years and supports Google only.
I would recommend dns-over-https [1] instead which has support for multiple protocols and is still actively maintained.
Note that Google announced [2] yesterday that they recommend to use the newer IETF protocol (at a new endpoint), which is also the protocol of all other major DoH providers (CloudFlare, Quad9, etc).
[1] https://www.archlinux.org/packages/community/x86_64/dns-over-https/ [2] https://security.googleblog.com/2019/06/google-public-dns-over-https-doh.htm...
-- Regards, Felix Yan
Hi small addition: It's also possible to use DNS-over-TLS with systemd-resolved[2] as alternative to DNS-over-HTTPS. chris [2] https://wiki.archlinux.org/index.php/Systemd-resolved
participants (2)
-
Christian Rebischke
-
Felix Yan