Comment on Ideas wanted
midas@ymmel.nl 1 year ago
Not sure if I completely understand but I think you want public service 1 accessible on subdomains s1.domain.com and internal service 2 on s2.domain.com?
Just point the A record for s2 to an internal ip address (or a tailscale ip). The only thing dns does is translate a (sub)domain to an ip address. So outside of your network s2.domain.com wouldn’t resolve but inside your network it would.
That’s what I did:
*.selfhosting.domain.tld that points to my router’s IP address, which then redirects to an nginx+certbot reverse proxy*.local.domain.tld that points to my local IP with CaddyThe only challenging part was to configure Caddy to issue SSL certificates using the DNS challenge since *.local.domain.tld isn’t exposed to the outside world.
subdomains would work, though ive never worked on it without a gui. Time to do some learning i guess :)
OK, I didn’t read before answering, probably ignore my answer below but I’ll leave it up incase someone learns something from it.
EncryptKeeper@lemmy.world 1 year ago
Or just louse one, and then run a local DNS resolver like pihole or AdGuard home and just make a record for the same host locally. The local DNS resolver will resolve the local request before it reaches the public DNS.