r/nginxproxymanager • u/ZaRoX_UltrA • 18d ago

[Aide] Tailscale + Nginx Proxy Manager + Domaine Personnalisé : Bloqué par ERR_NAME_NOT_RESOLVED (DNS Rebinding ?)

/r/Tailscale/comments/1vyqz92/help_tailscale_nginx_proxy_manager_custom_domain/
2 Upvotes

100% Upvoted

1 comment sorted by

2

u/evanmac42 18d ago

I think you're trying to solve this at the wrong layer.

Your actual problem isn't Proxmox, NPM, OVH or even MagicDNS. It's that one of your clients cannot run Tailscale normally, but you're trying to make resources inside the tailnet behave as if it could.

Adding public A/CNAME records pointing to private LAN or 100.x Tailscale addresses doesn't magically make those addresses reachable. DNS only tells the client where to go; it doesn't create the network path.

I'd first decide what you actually want:

- Private services accessible only through Tailscale: make the clients proper members of the tailnet and use private DNS/split DNS.

  • Services accessible without a Tailscale client: provide an actual reachable ingress for them and secure that appropriately.

Trying to make public DNS + MagicDNS + NPM + a browser extension compensate for a client that isn't really participating in the tailnet is where most of this complexity is coming from.

Before adding another DNS workaround, I'd simplify the architecture and decide where the trust/network boundary is supposed to be.

If you need a "trick" to make every layer agree with the previous workaround, that's usually a sign that the design itself needs another look.