Windows 10: Does the latest public windows build (20H2) support DNS over HTTPS?

/u/the_green_grundle · Dec 16, 2020

Or is it still just the preview builds that have that? Thanks in advance.

submitted by /u/the_green_grundle
[link] [comments]

:)

Hybrid_theory · Dec 16, 2020

DNS problems with router

A couple suggestions I have for you:

Update the firmware on the router. Maybe it's getting into a badstate, and a firmware update might fix it. Or if you're comfortable with it, install a custom firmware like dd-wrt. Just make sure its supported on your router first.

Change your DNS to: 8.8.8.8, 4.2.2.1. Might help.

If none of these work, maybe statically set your DNS on your PS3/PC to the IPs you listed, taking the router out of the lookup procedure.

Last option, is look for a new router.

Brink · Dec 16, 2020

Windows 10 will improve user privacy with DNS over HTTPS

Here in Windows Core Networking, we’re interested in keeping your traffic as private as possible, as well as fast and reliable. While there are many ways we can and do approach user privacy on the wire, today we’d like to talk about encrypted DNS. Why? Basically, because supporting encrypted DNS queries in Windows will close one of the last remaining plain-text domain name transmissions in common web traffic.

Providing encrypted DNS support without breaking existing Windows device admin configuration won't be easy. However, at Microsoft we believe that "we have to treat privacy as a human right. We have to have end-to-end cybersecurity built into technology."

We also believe Windows adoption of encrypted DNS will help make the overall Internet ecosystem healthier. There is an assumption by many that DNS encryption requires DNS centralization. This is only true if encrypted DNS adoption isn’t universal. To keep the DNS decentralized, it will be important for client operating systems (such as Windows) and Internet service providers alike to widely adopt encrypted DNS.

With the decision made to build support for encrypted DNS, the next step is to figure out what kind of DNS encryption Windows will support and how it will be configured. Here are our team's guiding principles on making those decisions:

Windows DNS needs to be as private and functional as possible by default without the need for user or admin configuration because Windows DNS traffic represents a snapshot of the user’s browsing history. To Windows users, this means their experience will be made as private as possible by Windows out of the box. For Microsoft, this means we will look for opportunities to encrypt Windows DNS traffic without changing the configured DNS resolvers set by users and system administrators.

Privacy-minded Windows users and administrators need to be guided to DNS settings even if they don't know what DNS is yet. Many users are interested in controlling their privacy and go looking for privacy-centric settings such as app permissions to camera and location but may not be aware of or know about DNS settings or understand why they matter and may not look for them in the device settings.

Windows users and administrators need to be able to improve their DNS configuration with as few simple actions as possible. We must ensure we don't require specialized knowledge or effort on the part of Windows users to benefit from encrypted DNS. Enterprise policies and UI actions alike should be something you only have to do once rather than need to maintain.

Windows users and administrators need to explicitly allow fallback from encrypted DNS once configured. Once Windows has been configured to use encrypted DNS, if it gets no other instructions from Windows users or administrators, it should assume falling back to unencrypted DNS is forbidden.

Based on these principles, we are making plans to adopt DNS over HTTPS (or DoH) in the Windows DNS client. As a platform, Windows Core Networking seeks to enable users to use whatever protocols they need, so we’re open to having other options such as DNS over TLS (DoT) in the future. For now, we're prioritizing DoH support as the most likely to provide immediate value to everyone. For example, DoH allows us to reuse our existing HTTPS infrastructure.

For our first milestone, we'll start with a simple change: use DoH for DNS servers Windows is already configured to use. There are now several public DNS servers that support DoH, and if a Windows user or device admin configures one of them today, Windows will just use classic DNS (without encryption) to that server. However, since these servers and their DoH configurations are well known, Windows can automatically upgrade to DoH while using the same server. We feel this milestone has the following benefits:

We will not be making any changes to which DNS server Windows was configured to use by the user or network. Today, users and admins decide what DNS server to use by picking the network they join or specifying the server directly; this milestone won’t change anything about that. Many people use ISP or public DNS content filtering to do things like block offensive websites. Silently changing the DNS servers trusted to do Windows resolutions could inadvertently bypass these controls and frustrate our users. We believe device administrators have the right to control where their DNS traffic goes.

Many users and applications that want privacy will start getting the benefits without having to know about DNS. In line with principle 1, the DNS queries become more private with no action from either apps or users. When both endpoints support encryption, there’s no reason to wait around for permission to use encryption!

We can start seeing the challenges in enforcing the line on preferring resolution failure to unencrypted fallback. In line with principle 4, this DoH use will be enforced so that a server confirmed by Windows to support DoH will not be consulted via classic DNS. If this preference for privacy over functionality causes any disruption in common web scenarios, we’ll find out early.

In future milestones, we'll need to create more privacy-friendly ways for our users to discover their DNS settings in Windows as well as make those settings DoH-aware. This will give users, device admins, and enterprise admins the ability to configure DoH servers explicitly.

Why announce our intentions in advance of DoH being available to Windows Insiders? With encrypted DNS gaining more attention, we felt it was important to make our intentions clear as early as possible. We don’t want our customers wondering if their trusted platform will adopt modern privacy standards or not.

If you are interested in joining the larger industry conversation about encrypting the DNS, check out one of the IETF working groups working with DNS (ABCD, Apps Doing DNS, DNSOP, DPRIVE) or the new Encrypted DNS Deployment Initiative.
Click to expand...

Source: https://techcommunity.microsoft.com/...S/ba-p/1014229

Brink · Dec 16, 2020

Firefox DNS over HTTPS rollout begins for US users

@: you may want to update the pix in Step 5 enable, of: How to Enable or Disable DNS over HTTPS (DoH) in Firefox It's missing the listing for NextDNS in the drop down, the post / thread in News (here) is okay.
Click to expand...

Thank you Steve. *Smile

I'll look at updating it now.

EDIT: Now updated. *Wink

Windows 10: Does the latest public windows build (20H2) support DNS over HTTPS?

Does the latest public windows build (20H2) support DNS over HTTPS?

Does the latest public windows build (20H2) support DNS over HTTPS?

Does the latest public windows build (20H2) support DNS over HTTPS?

Does the latest public windows build (20H2) support DNS over HTTPS? - Similar Threads - Does latest public

I cannot enable DNS over HTTPS

DNS over HTTPS in Windows 11

DNS over HTTPS in Windows 11

DNS over HTTPS on Windows 10

Enabling DNS over https in Edge

Windows 10 is getting DNS over HTTPS (DoH) support

DNS over HTTPS?

DNS-over-HTTPS (or DoH) Question

DNS over HTTPS with Firefox