4 ms·

Windows 11 does not allow using this combination

by baobabKoodaa 1y ago

snickerdoodle12 1y ago
Huh? Did they break the primary/secondary DNS server setup that has been present in all operating systems for decades?
- antonvs 1y ago
  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.
  - snickerdoodle12 1y ago
    What does that have to do with plain old dns?
    - antonvs 1y ago
      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.
AStonesThrow 1y ago
[dead]
lxgr 1y ago
How so? Does it reject a secondary DNS server that’s not in the same subnet or something similar?
- antonvs 1y ago
  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.
  - lxgr 1y ago
    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 https://<ip>/foo" would yield https://1.1.1.1/foo https://1.1.1.1/foo? If so, why not just allow providing an actual URL for each server?
    - antonvs 1y ago
      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.
      - lxgr 1y ago
        Very cool, thank you!
antonvs 1y ago
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 https://cloudflare-dns.com/dns-query 9.9.9.9: https://dns.quad9.net/dns-query https://dns.quad9.net/dns-query 8.8.8.8: https://dns.google/dns-query https://dns.google/dns-query See https://learn.microsoft.com/en-us/windows-server/networking/dns/doh-client-support https://learn.microsoft.com/en-us/windows-server/networking/... for info on how to set the templates.
- baobabKoodaa 1y ago
  Awesome! Thank you!
  - antonvs 1y ago
    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 https://github.com/Curious4Tech/DNS-over-HTTPS-Set-Up

Windows 11 does not allow using this combination

snickerdoodle12 1y ago

Huh? Did they break the primary/secondary DNS server setup that has been present in all operating systems for decades?

antonvs 1y ago
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.
- snickerdoodle12 1y ago
  What does that have to do with plain old dns?
  - antonvs 1y ago
    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.

AStonesThrow 1y ago

[dead]

lxgr 1y ago

How so? Does it reject a secondary DNS server that’s not in the same subnet or something similar?

antonvs 1y ago
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.
- lxgr 1y ago
  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 https://<ip>/foo" would yield https://1.1.1.1/foo https://1.1.1.1/foo? If so, why not just allow providing an actual URL for each server?
  - antonvs 1y ago
    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.
    - lxgr 1y ago
      Very cool, thank you!

antonvs 1y ago

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 https://cloudflare-dns.com/dns-query 9.9.9.9: https://dns.quad9.net/dns-query https://dns.quad9.net/dns-query 8.8.8.8: https://dns.google/dns-query https://dns.google/dns-query See https://learn.microsoft.com/en-us/windows-server/networking/dns/doh-client-support https://learn.microsoft.com/en-us/windows-server/networking/... for info on how to set the templates.

baobabKoodaa 1y ago
Awesome! Thank you!
- antonvs 1y ago
  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 https://github.com/Curious4Tech/DNS-over-HTTPS-Set-Up