
Do you have a plan for reverse DNS for 44net Connect tunnels? It would be handy to have that work, or if there are specifics of how to handle any sort of DNS to have that spelled out (including "we don't do that", that's an OK answer).
I know you need some guardrails to make it work (e.g. no A records with PTR records pointing to google.com)
I put together a self-hosted web server on a #44net address, using nginx and certbot for HTTPS service, a tiny but mighty Pi 1 as the physical host, and ufw as a host firewall. It lives at home, no change to my home firewall.
The real challenge I had was realizing the attack surface of such a #44net tunnel. Getting a good firewall configuration set up first and not as an afterthought is critical because the Internet is a difficult place.
@ARDC needs more docs / tutorials on same.