@dany_wilde If the actual requirement is to access directly via a domain name, you can achieve it by modifying the hosts file on the client machine, or if you have a registered domain, you can use public DNS to resolve it to the virtual IP assigned by the mesh network. If you want to deploy a DNS service on ZimaOS, I recommend trying AdGuardHome (just a personal preference).
If you also need to enable an application to be accessed through a subdomain name, you need to separately configure the front reverse proxy and point a subdomain name to the corresponding port.
I’m hosting apps via Nginx and Cloudflare (“Cloudflared” tunnel connection).
I wanted to run some of my apps through a VPN.
I found a VPN (WireGuard).
Unfortunately, AdGuard Home doesn’t seem to be 100% compatible.
So I looked for a domain name manager that I could use on my NAS alongside the VPN and in place of AdGuard Home.
This would be possible, but it requires changing the port and IP address of AdGuard Home and replacing it with this utility (CoreDNS , CoreDNS ), which would then use AdGuard Home’s port (53) as well as its IP address (that of the NAS).
This makes the solution much more complicated.
I’m wondering if I shouldn’t just give up on the idea of a DNS server behind WireGuard.
The solution—keeping AdGuard Home for DNS filtering—is far too complex for me, and I’m seriously wondering if any of this is even feasible in my case.