João Lúcio@dmoren Regarding yout subdomain you can just use Synology’s DDNS and point the subdomain to that address with a CNAME. It works for the SSL certificate (you need to open port 80 and maybe 443).
Dan Moren@joaolucio Not quite sure what you mean. I'm using a custom DDNS, which requires a little more effort in terms of updating the IP if changes.
@dmoren you can use that or just set it using synology’s own DDNS. It gives you a name.synology.me and then point the subdomain to that URL using a CNAME record on your domain/host DNS. With this you don’t need extra DDNS services, scripts or to login every 30 days.
@joaolucio Yeah, I just prefer having it on my own domain.
@dmoren Maybe I’m not understanding but I have my own domain on my NAS with a valid SSL certificate. The DDNS domain is just needed to point the subdomain to it. I use the subdomain for everything: SMB, web, etc. It’s not a redirect.
@joaolucio I think just configuration differences? I’m using a subdomain of my main domain pointing at the NAS and via DDNS. I do have a cert on it, and it works, it’s just finicky.
@dmoren on The Rebound I though I heard the cert was self signed. Nevertheless this method is bullet proof and it just works. No extra scripts or having to correct things.
@joaolucio The Synology cert is self signed. But that only applies if you access on the local Bonjour name.
@dmoren I think that’s what I don’t get. My setup is not finicky at all. Is your subdomain pointing to the IP directly?
@joaolucio I think we’re just talking at cross purposes. Everything works fine.