So, I've decided to configure my Synology NAS to perform forward and reverse DNS for my internal network.

I, and others, Ubiquiti claimed, multiple times, to be fixing it and never did. I eventually gave up on Ubiquiti ever properly fixing this issue. Finally, even if you specify an alias via the USG configuration, that alias will be ignored in favor of the way the host identified itself to the DHCP server initially (no matter how broken, like having spaces), and resolution will fail. If you have to manually assign an IP address, it will not register in DHCP, so resolution will fail. There is no where to configure a default domain name (search domain) and if you use a Fully Qualified Domain Name (FQDN), resolution will fail. If there's a space, then there's a space (and resolution will fail). When setting up a FTP connection to my Synology.Д«asically, however your device identifies itself to the DHCP server on the USG is how it will be inserted into DNS. Unless you point it to a WINS server in the Event setup for NAS or other. This is a problem they've had with their UniFi Security Gateway (USG) for quite some time, as documented.ДЇrustrated! Can't get 'Server Type.

However, one area that Ubiquiti really falls down on is internal DNS resolution of DHCP hosts. I'm a big fan of the Ubiquiti UniFi networking gear, I wrote about how I was able to use their gear to of my IoT devices from the rest of my network.

Synology wins server setup