FTLDNS on Synology

This is harmless, the file simply does not exist.

This is harmful, try running

sudo setcap CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_NET_ADMIN+eip /usr/bin/pihole-FTL

and then try again to see if this fixes it.

This is expected as the previous setcap failed. For your safety, FTL runs completely unprivileged (in contrast to dnsmasq which is started as root process). Hence, we need to add additional capabilities beforehand to allow it to bind to port 53, etc.