I come from the Ubuntu context: there installing a package named kind of ntp was generally enough to ensure time synchronization. Today I performed another of my early Rocky Linux installations and I suspect I unintentionally skipped setting an option that would bring that functionality with no other action required. Installing afterwards a package name chrony didn’t help. I might have some firewall between the machine and the external NTP servers, though apparently the first time I installed this matter went smoothly - I did not find the clock set at a presumably GMT time.
Chrony uses port udp/323 whereas ntp uses udp/123. So if your firewall does block chrony, then you would need to unblock outgoing access for udp/323.
You can use as an alternative systemd-timesyncd, so:
dnf install systemd-timesyncd
which apparently will use ntp and therefore udp/123. You will of course then need to disable chrony service or remove it, and then enable the systemd-timesyncd service and start it.
Asterisk showing the server with whom client is currently syncing.
Value under Reach column is important. Its should be 377 ( This is in octal , In binary it will be converted to 11111111 ) which literally display the information about last 8 times syncing status ( 1 mean it was successful and 0 mean get failed due to some reason )
Chrony will not change your time zone. If you need to set time zone . you may set by