DNS-over-HTTPS Policy Requirements for Resolvers

Re:DNS-over-HTTPS Policy Requirements for Resolvers by localhostdotdev on Wednesday April 10, 2019 @09:24AM (#19624376)

pretty cool, I wished chrome did that. firefox is probably going to choose cloudflare (1.1.1.1).

I wonder how this plays out with local DNS (e.g. my ISP has some custom domains for me to use, and internal company network addresses)

[ Parent | on HN ]

Re:DNS-over-HTTPS Policy Requirements for Resolvers by afiori on Wednesday April 10, 2019 @09:43AM (#19624517)

You can set firefox to use the normal DNS as a fallback

[ Parent | on HN ]

Re:DNS-over-HTTPS Policy Requirements for Resolvers by teddyh on Wednesday April 10, 2019 @12:14PM (#19626118)

One could reasonably wonder why “normal” should be a fallback.

[ Parent | on HN ]

Re:DNS-over-HTTPS Policy Requirements for Resolvers by afiori on Wednesday April 10, 2019 @01:14PM (#19626756)

I have two reason to like DoH: public wifi blocking sites and ISPs blocking sites. I understand that it is "wrong" from the perspective of a network stack, but for my use case that is far from being even a weak issue.

[ Parent | on HN ]

Re:DNS-over-HTTPS Policy Requirements for Resolvers by gpm on Wednesday April 10, 2019 @01:17PM (#19626787)

Because "normal" = "insecure and not private"? "Legacy" might be a better name for it in the near future.

[ Parent | on HN ]