ARCHITECTURE MERGEDWhy this needs careful design
DNS and reverse proxying are related—but they are not the same layer.
NetworkBridge would need to coordinate multiple networking components rather than trying to make DNS itself perform proxy behavior.
ClientRequests app.home or server.home
↓
DNS LayerResolves the requested name to the appropriate network endpoint
↓
Routing / Proxy LayerHandles HTTP/HTTPS service routing where needed
↓
Host / ServiceReceives traffic on the intended internal port
Key design goal
Do not break direct access while simplifying application access.
A hostname used for SSH should still behave like a host. A friendly application hostname can route web traffic to an internal port. Those are different use cases and the system should model both explicitly.
Important: Generic TCP/UDP forwarding, SNI-based routing, firewall/NAT behavior, and HTTP reverse proxying have different constraints. The final architecture would need to respect those differences.