3 ms·
I think it's feasible to have a domain with certificate for resolving any ip, using dnsmasq as DNS resolver for that domain, combining this https://pfigue.gith
by DiThi 11y ago
I think it's feasible to have a domain with certificate for resolving any ip, using dnsmasq as DNS resolver for that domain, combining this
https://pfigue.github.io/blog/2013/12/06/configuring-dnsmasq-to-serve-my-own-domain-name-zone/ https://pfigue.github.io/blog/2013/12/06/configuring-dnsmasq... (but without --server)
and this
https://stackoverflow.com/questions/28204678/dns-service-to-dynamically-resolve-subdomain-to-a-custom-ip-address https://stackoverflow.com/questions/28204678/dns-service-to-... (specifically, the "synth-domain" parameter, maybe limiting it to LAN ip addresses)
I haven't tried it.
- greggman 11y agoI'm not really sure how that would help. Wouldn't all the phones be getting their DNS from the local router? How would that work without having each users have to configure DNS on their phones? Also how does running DNS server help? I don't expect people to know how to configure their router to point to some DNS server running on their local PC. Maybe I'm mis-understanding the suggested solution
- DiThi 11y agoThe application redirects to <local https host>, and to make the certificate valid, have a wildcard *.example.com. With the DNS server you can have e.g. https://192-168-0-7.example.com/ https://192-168-0-7.example.com/ resolve to 192.168.0.7. All of this, of course, only if there are some desired HTTPS-only features in the browser.