Just wanted to make mention of an issue I resolved with NTP on unRaid so if others run into the same issue this might help.
The issue was when using a hostname in the NTP custom settings in unRaid, and checking the console with ntpq -p I was seeing that the host I entered was dwelling on the .INIT. state, and not actually syncing with my local NTP server.
It turns out, this was because the hostname I used resolves both an A and an AAAA entry (IPv4 / IPv6) and it was trying over IPv6 by default and failing.
When you make alterations to the custom NTP server fields in the web GUI and save, the system copies the template config from /etc/ntp.conf- appending the custom server entries at the bottom.
In this template file, I found near the bottom and commented out interface ignore ipv6.
Then, once I re-added my local NTP server's hostname in the web GUI and saved, the changed I made in the 'template' were applied and the ntpq -p revealed it was syncing properly and all was well.
Was there any particular reason to ignore ipv6 other than it's still gaining in popularity and not everyone uses it?
Perhaps moving forward should this line be excluded or commented for future releases?