6 ms·

Firefox Nightly lets you set the DoH server in network settings: https://i.imgur.com/wBAtJ7Z.png https://i.imgur.com/wBAtJ7Z.png. Note that this is still an ex

Firefox Nightly lets you set the DoH server in network settings: https://i.imgur.com/wBAtJ7Z.png https://i.imgur.com/wBAtJ7Z.png. Note that this is still an experimental feature, so when this ships it won’t necessarily default to Cloudflare nor be enabled by default.

vetinari 8y ago
Manually setting it in about:config is not good enough. When you connect to a network that needs its own DNS to access its resources, you are not going to change that setting each time you connect to that network. Even more interesting thing happens, when you physically roam between several of such networks (for example: your company and your customer). What was until now handled transparently handled by DHCP for you, now you have to manually configure each time you connect to that another network. Now, we have moved from static network config decades ago, and for a good reasons.
- dagenix 8y ago
  That assumes that you can trust the networks you connect to. There is a lot of evidence available that there are a lot of networks out there that should not be trusted.
  - xg15 8y ago
    Indeed - which is why e.g. Windows asks you whether your LAN/Wifi is a "home network", "work network" or "public network". You could use the same strategy to find out whether or not you should trust the networks DNS settings.
    - j0057 8y ago
      Assuming DNS resolution still happens in the OS, this is actually a somewhat sensible suggestion! Use DoH on public WiFi (although basic network hygiene suggests you should really use a VPN there), and use the DHCP-provided DNS server on home and work networks.
      - sroussey 8y ago
        At home, the cable company is just as bad (or the same as) the mobile operator. Neither of these scenarios do you want to trust your ISP, or add to their profile of you. At work though, probable the opposite.
  - josteink 8y ago
    > That assumes that you can trust the networks you connect to. Which an overwhelming part of the world does. Forced DoH is making problems for the clear majority when trying to solve a minor problem for a tiny majority. Clearly that's not going about things the right way. Anyhow: If you don't trust a network... Why are you connecting to it?
    - dagenix 8y ago
      I don't trust most of the networks I connect to. Home network - nope, I don't want to use Verizon's DNS servers; subway wifi - no; Coffee Shop - lol, no. Etc. Why should I have to trust the network I'm connecting to? That seems like a major violation if the end to end principle. It's also just impractical. If the overwheming majority of the wild trusts the networks they are connecting to, that seems like pretty good evidence that DoH or something like it has value.
- bugmen0t 8y ago
  But this isn't about:config. This is in settings.
xg15 8y ago
This is a good start, but I don't see why you couldn't make it autoconfigurable like normal DNS is. I suspect, few users will have anything useful to put in that field, except the default.
- zaarn 8y ago
  Normal DNS is autoconfigured via DHCP. The browser doesn't have access to the DHCP data because it usually happened during the OS startup way before the desktop even becomes visible. That doesn't stop you from using a custom DHCP option.

vetinari 8y ago

Manually setting it in about:config is not good enough. When you connect to a network that needs its own DNS to access its resources, you are not going to change that setting each time you connect to that network. Even more interesting thing happens, when you physically roam between several of such networks (for example: your company and your customer). What was until now handled transparently handled by DHCP for you, now you have to manually configure each time you connect to that another network. Now, we have moved from static network config decades ago, and for a good reasons.

dagenix 8y ago
That assumes that you can trust the networks you connect to. There is a lot of evidence available that there are a lot of networks out there that should not be trusted.
- xg15 8y ago
  Indeed - which is why e.g. Windows asks you whether your LAN/Wifi is a "home network", "work network" or "public network". You could use the same strategy to find out whether or not you should trust the networks DNS settings.
  - j0057 8y ago
    Assuming DNS resolution still happens in the OS, this is actually a somewhat sensible suggestion! Use DoH on public WiFi (although basic network hygiene suggests you should really use a VPN there), and use the DHCP-provided DNS server on home and work networks.
    - sroussey 8y ago
      At home, the cable company is just as bad (or the same as) the mobile operator. Neither of these scenarios do you want to trust your ISP, or add to their profile of you. At work though, probable the opposite.
- josteink 8y ago
  > That assumes that you can trust the networks you connect to. Which an overwhelming part of the world does. Forced DoH is making problems for the clear majority when trying to solve a minor problem for a tiny majority. Clearly that's not going about things the right way. Anyhow: If you don't trust a network... Why are you connecting to it?
  - dagenix 8y ago
    I don't trust most of the networks I connect to. Home network - nope, I don't want to use Verizon's DNS servers; subway wifi - no; Coffee Shop - lol, no. Etc. Why should I have to trust the network I'm connecting to? That seems like a major violation if the end to end principle. It's also just impractical. If the overwheming majority of the wild trusts the networks they are connecting to, that seems like pretty good evidence that DoH or something like it has value.
bugmen0t 8y ago
But this isn't about:config. This is in settings.

xg15 8y ago

This is a good start, but I don't see why you couldn't make it autoconfigurable like normal DNS is. I suspect, few users will have anything useful to put in that field, except the default.

zaarn 8y ago
Normal DNS is autoconfigured via DHCP. The browser doesn't have access to the DHCP data because it usually happened during the OS startup way before the desktop even becomes visible. That doesn't stop you from using a custom DHCP option.