Linking Domain name to DS212

[waruta]

Hi all,

This may seem like the noobiest of noob questions, but I've been having issues since last week regarding accessing my NAS from the internet. Currently, the NAS is hiding behind a router and I have used EZ-Internet to forward ports and can access it using the IP from outside with no issue.

What I am confused is the DDNS and Subdomain + SSL issues. The Synology DDNS doesn't forward to my IP/internal IP at all. I do have a private domain and can make unlimited subdomains which I have. So currently I have www.mydomain.com and nas.mydomain.com; how am I supposed to route nas.mydomain.com to my nas IP?

Since I can only use a redirect html page inside the root of nas.mydomain.com, the SSL certificate shows up as an error (of course) as it re-routes to a page that is not covered by the original SSL cert.

So in conclusion, I need to know how to point my subdomain to my NAS hiding behind the router and fix the SSL issues at the same time....

Thank you for the time.

Regards,

w.

[axj]

You have to look at the 'Virtuel host', I think!

[waruta]

I don't think Virtual Host works in this case. I know that if you have the capability, CNAME or A records will help point the subdomain to a certain IP, but the issue I'm having is that my fiber connection keeps getting a new IP address every 24-48 hours, and even with setting the EZ-INternet or NAS connection properly, I get the message "port re-mapping must be added".

I cannot change CNAME or A records with my domain/subdomain either...so I'm kind of lost as what to do...maybe I'm not creating a proper static IP or address for the NAS through this POS router?

Regards,

w.

[canadaguy2012]

Here's how I did it:

1. set up the Synology dynamic DNS to give me an address of XYZ.synology.me, where the IP address is automatically updated.

2. set up a CNAME record at my DNS provider so that a subdomain of mydomain.com (subdomain.mydomain.com) is pointed at XYZ.synology.me

3. set up the correct port forwarding on my router

That's it. Now, when you are outside the LAN and type in subdomain.mydomain.com, the DNS records will point the query at XYZ.synology.me, which will in turn point your request at your router's current IP address.

As a (desirable) side effect, this also solves the certificate error problem that some people have reported. If your SSL certificate (e.g. through StartSSL, which gives you a free certificate) is for subdomain.mydomain.com, when you use the above method, your browser thinks it is directly connected to subdomain.mydomain.com and not a mismatched domain. (If you connect to XYZ.synology.me, the SSL certificate is for subdomain.mydomain.com and the browser will throw up a warning due to the certificate mismatch).

[myCloud]

My domain name is registered with GoDaddy, with the registry details hidden at secureserver.com. For years, http://www.my_domain.com has been redirected with masking to web.mac.com. With MobileMe web hosting going away, I redirected iWeb to host my site on the DiskStation, which has a DDNS of something.familyds.org, a Synology domain. It was a simple matter at GoDaddy to change the redirection to something.familyds.org and ensure the CNAME record for www pointed there. This can take some time to propagate throughout the DNS system.

Getting a StartSSL server certificate for my_domain.com was easy--way easier than the 10 easy steps post. The hardest part may be realizing you have to go through the tabs in the STARTSSL control panel from right to left. There are some email confirmations to do and I particularly like that it lets you use the my_domain.com@secureserver.com for the certificate email address for privacy.

The install on the disk station was easy, using the DiskStation Control Pane HTTPS section, and I even used the intermediate server certificate.

Port 80 and port 443 needed to be forwarded in the router to their same DiskStation ports, in addition to whatever I had set up for DSM access. In my case all other ports are accessed via VPN.

That's how I did it.

[waruta]

I can't change CNAME records or DNS anything for that matter through our domain guys, so I guess I'm stuck with the security exception that occurs when nas.mydomain.com gets pointed to nas.synology.me *sigh* ...wish it was easier.

[HarryPotter]

viewtopic.php?f=145&t=15586&p=67063&hilit=mydomain#p67063
viewtopic.php?f=145&t=21390&p=86321&hilit=mydomain#p86321