Re:Firefox’s Trusted Recursive Resolver DNS feature is dange...
by topranks on Sunday August 05, 2018 @03:15PM
(#17692928)
That’s really the issue I think, has to be a public server if it’s going to work for mobility.
Fixed desktops maybe, but a laptop or phone?
Re:Firefox’s Trusted Recursive Resolver DNS feature is dange...
by pastage on Sunday August 05, 2018 @05:56PM
(#17693767)
Split horizon was always a bad hack, there has always been alternatives. DoH could be used on the default DNS servers too, there is value of encrypted DNS on LAN as well.
Re:Firefox’s Trusted Recursive Resolver DNS feature is dange...
by vetinari on Monday August 06, 2018 @05:56AM
(#17696311)
> Split horizon was always a bad hack, there has always been alternatives.
I always see this repeated as a mantra, but never it's rationale. No company is going to advertise their internal infrastructure needlessly. There's no upside in the world knowing that your _kdc._tcp.company.com is 192.168.10.20; but there are downsides.
> DoH could be used on the default DNS servers too, there is value of encrypted DNS on LAN as well.
Sure, but hardcoding or statically-configuring the value is not the way. LANs need to have their DHCP tags respected. If one of them is "use this URL for DoH-server", that's fine.
What is THE problem, is configuring the browser. No one is going to reconfigure their browser after each connection to a different network. There's a reason why we moved from static configuration towards DHCP, which can configure network-specific settings. DNS is a network-specific setting, and Mozilla is breaking it.