In this blog post, i will show you how to map your Synology http address to your own domain, even if you don’t have a static IP address.
If you dont have a static IP address, you are using a Dynamic name service provider like no-ip or synology’s own service. Those services provide you with the address you currently use to access your synology outside your network.
So in this tutorial I will show you how to access your Synolgoy with your own subdomain:
From: mydomain.synology.me to subdomain.mydomain.com
Buy a domain name
First of all, buy or login to your domain name provider. I use Hover for all my domain names.
If you also want to register your domain at Hover, click on this link or the picture below for a 2$ discount, when you sign up an account with them. Disclosure: I get also $2 discount, thanks!! 🙂
Get a $2 discount if you purchase your domain with Hover
Create a subdomain and point it to your Synology
You don’t need to create a subdomain, but I use the main domain for a website, so I created a subdomain in hover for my diskstation: ds.yourdomainname.com
So, If your domain name is example.com, we will create a subdomain named: ds.example.com
Let’s do that in Hover:
- Hostname: Add your subdomain
- Record type: CNAME
- Target host: Your current address: yourdomain.synology.me
Now you can login with your own domain:
ds.mydomain.com:5000
Secure your Synology with SSL encryption (or https)
The main reason for doing this for me, was to enable the possibility to add a SSL certificate and encrypt all my communications to and from the Synology.
Something doesn’t seem right. You created a sub domain ds.domain.com and then said you can access your Nas through domain.com:5000? I might be confused but I think you may have some typos in this post. Isn’t it supposed to be ds.domain.com:5000?
I am not an expert in domains…so I cant tell, but it works for me.
/Ruth
If you are not an expert, then don’t pretend to be. Your guides are flawed with errors and don’t provide meaningful steps to follow.
Hi Eric, I don’t pretend to be an expert because I am not, quite the opposite. I just document what works for me hoping it will work for others in simple words and clear steps.
If my guide didn’t work for you, make sure to look elsewhere, you will find your answer soon. Best wishes, Ruth
Hi Ruth,
Thanks so much for putting this together.
I’m having some issues setting up my subdomain with Hover, however. Per your directions, I’ve added a CNAME record with a subdomain that points to my DDNS address. But it just does not connect. I am told that the server’s DNS record cannot be found when I visit subdomain.domain.net. Is this the sort of thing that might take 24 hours to propagate? Do I need to specify a subdomain at my DDNS provider?
I should note that I actually already set up Let’s Encrypt for my domain prior to creating the subdomain. Do you think this could be the issue? I would expect that it should simply indicate that subdomain.domain.net is not properly secured and still allow access. I also do not see a way to edit my Let’s Encrypt certificate in DSM6 to include the subdomain as a valid address. Do you know how to do this?
Right now, I’m able to get to mydomain.net:5001 and it shows https: and reveals the certificate is authenticated by Let’s Encrypy, so it looks like I am properly set up on the main domain.
Lastly, do you know how I can set the domain to automatically go to port 5001? Currently, I always have to specify the port after typing the url, which is obviously very inconvenient. I know that this can be done but I’m just not sure of the literal logistics either with Hover or my DDNS provider or even where I should be doing this.
Thanks,
Rob
Sorry, being away from this blog for a while. Did you solve your issue?
/Ruth
Hi Ruth,
Thanks so much for putting this together.
I’m having some issues setting up my subdomain with Hover, however. Per your directions, I’ve added a CNAME record with a subdomain that points to my DDNS address. But it just does not connect. I am told that the server’s DNS record cannot be found when I visit subdomain.domain.net. Is this the sort of thing that might take 24 hours to propagate? Do I need to specify a subdomain at my DDNS provider?
I should note that I actually already set up Let’s Encrypt for my domain prior to creating the subdomain. Do you think this could be the issue? I would expect that it should simply indicate that subdomain.domain.net is not properly secured and still allow access. I also do not see a way to edit my Let’s Encrypt certificate in DSM6 to include the subdomain as a valid address. Do you know how to do this?
Right now, I’m able to get to mydomain.net:5001 and it shows https: and reveals the certificate is authenticated by Let’s Encrypy, so it looks like I am properly set up on the main domain.
Lastly, do you know how I can set the domain to automatically go to port 5001? Currently, I always have to specify the port after typing the url, which is obviously very inconvenient. I know that this can be done but I’m just not sure of the literal logistics either with Hover or my DDNS provider or even where I should be doing this.
Thanks,
Rob
Sorry, being away from this blog for a while. Did you solve your issue?
/Ruth
Hi Ruth Pozuelo Martinez,
Great blog, thank you for sharing.
I’m trying to do the same thing by connecting my purchased domain name to my website, located on my Synology DS211. However, I can’t seem to accomplish all the steps, yet.
Is it possible for you to guide or help me along with slightly more elaborate steps? (perhaps via mail?)
For instance, do I have to apply the IP address located in my Domain name provider into THE external section of the DDNS on the Synology? (External address IPv4).
And how to manage this when using a Dynamic service provider (no-IP)?
Hope you find it to get back to me. Thanks in advance.
JG
I am a bit late answering this, so I can imagine it is already working for you?
/Ruth
Hola Ruth,
Espero que estés bien. Una consulta, tuviste algún problema para cargar las subpaginas o los posts de tu blog usando el dominio redireccionado desde Godaddy o similar?
Estuve verificando que hay que hacer una configuración para que cargen esas sub-páginas con el nombre de host DDNS y no con la IP local que es lo que me pasaba a mi.
Quisiera saber si tuviste algún problema con eso o funcionó de entrada?
Mil gracias!
Hola,
No, no tuve problemas y funciona bien.
Lo que si tengo problemas es con los enlaces públicos. Lo has solucionado?
Como lo hiciste?
/Ruth
Enlaces públicos todavía no probé por que no puedo conseguir hacer funcionar la carga de las paginas o del contenido del blog con mi nombre del dominio.
Que error tenés no resuelve directamente la dirección del link?
Has visto este artículo?
https://www.google.se/amp/s/synoguide.com/2016/04/15/use-your-own-domain-on-wordpress-website-hosted-on-synology/amp/
El problema que yo tengo es que me cambia la dirección de mi synology a la IP interna cuando van a descargar el archivo y google les da un error de seguridad!
/Ruth
Thanks for this and also the instructions on how to create the certificate.
One question: this worked fine on my current Synology with DSM 6.2.2. However I have an old Synology with DSM 4.0, and there already the domain name does not work. Both Synologys are using the Synology DDNS with a xxx.myds.me name. I created a CNAME for both of them, but while the one for the new Synology works fine, the one for the old one does not seem to redirect properly. A nslookup for that CNAME one shows an IP address associated with my hosting provider instead of the IP assocaited with xxx.myds.me.
Does this CNAME setup require some kind of special support from the Synology in the way it registers for the DDNS? Something that maybe was not yet present in DSM 4.0?
Regards, Robert
Great question! I checked synology official docs and could not find any limitations regarding DSM versions, so I am afraid I dont know. Try asking them or in a synology forum!
/Ruth