I don't know how to fix it, but the important thing is that DNS is updated. While your NAS will issue the request properly, and Namecheap will pick up the new IPv4 address, unfortunately DSM thinks the request has failed and you get a hate e-mail for every failure.
If you are also using Namecheap, you can add a customized DDNS service provider by using the following query URL: you add Namecheap as a service provider, you can use the rest of the wizard to set up automatic DDNS, use your domain name for host and user name, and the DDNS password you got from Namecheap's web console. You can also use another provider, and for some reason DNS-O-Matic is no longer supported in DSM 7.0.
Namecheap has an end point that allows you the update DNS records via a request, see documentation here. If you paid for static IP addresses then this is not necessary then again, if you are paying every month for them you must have done it for a reason. You want to add an "A+ Dyniamic DNS Record", write down the password, then head over to DSM Control Panel > External Access > DDNS and add a task such that your NAS will update your DNS record automatically with your external IP address. First thing you want to do is use it to set up DDNS, so that your domain resolves to your NAS. I am using Namecheap, but I imagine all vendors provide similar capabilities. Replacing that certificate with one from Let's Encrypt is pretty easy, and it was the first thing I did.įirst, you need to own a domain that you have control over its DNS records. Nobody is recognizing Synology as a certificate authority, so the certificates that come with the NAS is no good. You can tell a lot of commercial web sites, such as a certain taro chip company in Hawaii that I don't visit any more, run on an older version of Synology NAS. SSL Certificate and DDNSĪll Synology NAS come with a self-signed certificate that most web browsers don't like (definitely not Firefox, Safari, Edge, and Chrome).
Synology's Docker support is very nice, but taking away packages that used to be available in DSM 6.2 seems uncool. NAS hardware died before the drives, and by plugging them into new hardware (read instructions carefully, must remember order of drives), I was able to recover my data.ĭSM 7.0 is a little disappointing, but it forced me to learn more about Docker.
The HGST drives I brought after reading its reports have been working fine after 6 years, recording videos from 4 IP cameras 24-hours non-stop. Speaking of hard drives, Blackblaze has been publishing hard drive reliability reports regularly and they are very helpful.
I found memory upgrade a good investment, unlike hard drives, which all seem to die eventually. Upgrading memory gives you headroom to run more Docker containers, and Linux will happily use any available memory left for caching to improve overall performance. If you plan to run GitLab, for example, it'll consume 3GB of memory. For less than $90 you can buy official SO-DIMM and expand total memory of your NAS from 2GB to 6GB. However, it does mean you have to do the work of Docker- and DSM-wrangling, there is more opportunity to shoot yourself in the foot, and a lot more experimenting to get it working before you can really customize it.Ībove picture shows you location of the RAM slot, revealed when you remove the mounting caddy for hard disks. It doesn't mean you cannot get equivalent functionalities. Unfortunately for DSM 7.0, the number of supported third-party applications have decreased. However, you are paying for the management software, DSM, the third-party applications and you have to weight how much that is worth to you. Synology devices are pretty expensive, in my opinion. It comes down to the cost and ability to upgrade. In this article, I am going to document what I did with a new DS-220+ NAS. They come with DSM, which made most system administration tasks easy.