News for hackers. Stuff that matters.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by baobabKoodaa on Wednesday July 16, 2025 @07:37AM (#44581065)
Windows 11 does not allow using this combination
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by snickerdoodle12 on Wednesday July 16, 2025 @08:17AM (#44581381)
Huh? Did they break the primary/secondary DNS server setup that has been present in all operating systems for decades?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @09:08AM (#44581924)
DNS over HTTPS adds a requirement for an additional field - a URL template - and Windows doesn't handle defaulting that correctly in all cases. If you set them manually it works fine.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by snickerdoodle12 on Wednesday July 16, 2025 @09:13AM (#44581969)
What does that have to do with plain old dns?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @09:25AM (#44582079)
Nothing, but Windows can automatically use DNS over HTTPS if it recognizes the server, which is the source of the issue the other commenter mentioned.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by lxgr on Wednesday July 16, 2025 @08:19AM (#44581403)
How so? Does it reject a secondary DNS server that’s not in the same subnet or something similar?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @09:07AM (#44581913)
It's using DNS over HTTPS, and it doesn't default the URL templates correctly when mixing (some) providers. You can set them manually though, and it works.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by lxgr on Wednesday July 16, 2025 @03:52PM (#44586131)
Ah, this is for DoH, gotcha!

This "URL template" thing seems odd – is Windows doing something like creating a URL out of the DNS IP and a pattern, e.g. 1.1.1.1 + "https://<ip>/foo" would yield https://1.1.1.1/foo?

If so, why not just allow providing an actual URL for each server?

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @04:49PM (#44586628)
It does allow you to provide a URL for each server. The issue is just that its default behavior doesn't work for all providers. I have another comment in this thread telling the original commenter how to configure it.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by lxgr on Wednesday July 16, 2025 @06:37PM (#44587587)
Very cool, thank you!
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @09:06AM (#44581904)
You can use it, you just need to set the DNS over HTTPS templates correctly, since there's an issue with the defaults it tries to use when mixing providers.

The templates you need are:

1.1.1.1: https://cloudflare-dns.com/dns-query

9.9.9.9: https://dns.quad9.net/dns-query

8.8.8.8: https://dns.google/dns-query

See https://learn.microsoft.com/en-us/windows-server/networking/... for info on how to set the templates.

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by baobabKoodaa on Wednesday July 16, 2025 @10:35AM (#44582818)
Awesome! Thank you!
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by antonvs on Wednesday July 16, 2025 @12:25PM (#44584116)
You're welcome. btw I came across a description of doing it via the GUI here: https://github.com/Curious4Tech/DNS-over-HTTPS-Set-Up