What strategy shall I take if I wanted to use a dnscrypt with a public hotspot that requires login through a captive portal?
Such hotspots require DNS settings to point to their servers (via DHCP) so that they redirect the first browser request, before allowing normal network use.
Just after connecting to the network and obtaining DHCP settings (and even before successful authorisation to the portal) all services running on my PC (maybe even regular programs checking for updates) will try to "call home" via the hotspot's DNS servers. Which I want to avoid.
On the other hand having DNS set to local dnscrypt proxy will not allow me to get an authorisation from the portal.
Is there a solution?
I thought of chaining dnsmasq with dnscrypt (which is what I do anyway) and configuring an exception for a specified domain in dnsmasq configuration (which I would later access from a browser). But then I have to insert a specific IP into a config file, which would require me to check which DNS servers are set through DHCP.