How to configure automatic time synchronization with NTP on elementary OS
Clock drift can seem harmless until an application refuses a secure connection, package updates fail signature checks, or saved logs disagree with the time shown in another system. Network Time Protocol, or NTP, keeps the system clock aligned with reliable time servers. The clock itself operates in Coordinated Universal Time, while the time zone determines how that UTC value appears in dates, times and calendars.
On elementary OS, automatic NTP synchronization can use the built-in systemd-timesyncd service or a dedicated NTP daemon. The built-in client is simple and well integrated with systemd, making it suitable for most desktops. A dedicated daemon provides more detailed peer statistics and may suit administrators who want traditional NTP logs, custom server rules or compatibility with an existing network configuration.
Why clock accuracy matters on elementary OS
Modern Linux systems use timestamps for more than displaying the time in the top panel. Secure web connections depend on accurate clocks when validating certificates, while the Advanced Package Tool checks repository metadata and package signatures. File modification times, cron jobs, systemd timers and application logs also rely on a consistent clock. Even a discrepancy of several minutes can make troubleshooting unnecessarily confusing.
Australia spans several time zones. Perth uses UTC+8 throughout the year, Darwin is on Australian Central Time, and Brisbane remains on Australian Eastern Standard Time without daylight saving. Sydney and Melbourne change their displayed time twice a year, so a correct time zone still needs an accurate underlying UTC clock. The local NTP service should remain enabled throughout those changes.
These distinctions have practical consequences across the Australian market. Point-of-sale terminals in Melbourne cafés, warehouse scanners in Brisbane and transport systems handling interstate bookings may all produce records that are compared later by auditors or customers. A machine that silently drifts can place an otherwise valid transaction outside the expected time window, even when its own clock appears plausible.
Check the current time service
Begin by checking whether elementary OS already has a time service running. Open Terminal from the applications menu and run:
timedatectl status
timedatectl show -p Timezone -p NTP -p NTPSynchronized
systemctl status systemd-timesyncd --no-pager
The first command reports the system time, the configured time zone, whether the clock is synchronised and whether systemd-timesyncd is active. NTPSynchronized=yes is the important result once the network connection has been active for a short time. An incorrect time zone can produce NTPSynchronized=yes while the displayed clock still appears wrong, so both values need attention.
If systemd-timesyncd is not available, install it with sudo apt install systemd-timesyncd. This is uncommon on current elementary OS releases because the service is normally present as part of the base system. When a release changes service defaults, independent reporting such as NewsMDN Linux coverage can also help establish whether the behaviour is part of a wider distribution change.
Hardware-clock warnings from timedatectl should not be treated as proof that NTP is broken. Some firmware cannot maintain its clock accurately while the machine is powered off, but NTP will correct the operating system clock at the next startup. Avoid setting the hardware clock to local time unless a specific embedded setup requires it.
Configure the built-in NTP client
systemd-timesyncd is an NTP client even though its service name does not contain the word “NTP”. It obtains the time over the network and periodically corrects clock drift. For an ordinary elementary OS desktop, it offers the easiest route to automatic time synchronisation without installing another daemon.
Enable the service and ensure that network time is selected:
sudo timedatectl set-ntp true
sudo systemctl enable --now systemd-timesyncd
Next, edit its configuration file:
sudoedit /etc/systemd/timesyncd.conf
Within the existing [Time] section, replace any active primary server entry with an Australian pool:
[Time]
NTP=au.pool.ntp.org
FallbackNTP=0.pool.ntp.org
Keep only one [Time] section and avoid leaving an older active NTP= line alongside the new one. The au.pool.ntp.org address returns several Australian time servers, which reduces dependence on any single host. The global pool acts as a fallback if the Australian pool cannot be reached.
Restart the service and inspect its connection:
sudo systemctl restart systemd-timesyncd
timedatectl timesync-status
A successful result should show a synchronised server and a stable offset. If the status command reports that no servers were found, confirm that the machine has working internet access and that a VPN or captive portal is not blocking the time service.
Run a dedicated NTP daemon
A dedicated daemon is useful when an administrator needs detailed peer information, persistent logs or a configuration shared with other Linux hosts. It is also a sensible choice for systems that already operate an NTP infrastructure.
Current elementary OS releases use Ubuntu packages in which ntpsec replaces the older NTP implementation. Install it with:
sudo apt update
sudo apt install ntpsec
For older elementary OS releases based on Ubuntu 22.04, install ntp instead with sudo apt install ntp. The configuration file is /etc/ntpsec.conf for NTPsec and /etc/ntp.conf for the older package. In either file, replace the distribution’s default server entry with:
pool au.pool.ntp.org iburst
Do not run systemd-timesyncd and the dedicated daemon as competing clients on the same desktop. Switch to the dedicated service with:
sudo systemctl disable --now systemd-timesyncd
sudo systemctl enable --now ntpsec
Replace ntpsec with ntp when using an older release. Confirm the exact unit name with systemctl list-unit-files 'ntp*', since some installations expose a compatibility alias as well. View the connected time sources with sudo ntpq -p; if ntpq is not installed, install the small ntpq utility from the repositories.
Apply the correct Australian time settings
NTP supplies the correct UTC reference, but the IANA time zone controls daylight-saving rules and the offset shown on the desktop. Set the appropriate zone with a command such as:
sudo timedatectl set-timezone Australia/Sydney
Other useful identifiers include Australia/Melbourne, Australia/Brisbane, Australia/Adelaide, Australia/Perth, Australia/Darwin, Australia/Hobart and Australia/Lord_Howe. The identifier should match the relevant state or territory. Using Australia/Sydney for New South Wales is conventional, while Australia/Melbourne is also valid for Victoria.
Most eastern and southern states begin daylight saving on the first Sunday in October, when clocks move from 2 am to 3 am, and finish on the first Sunday in April, when they move back. Queensland and Western Australia do not make that change. Lord Howe Island uses a 30-minute daylight-saving shift, so it should not be treated like the one-hour zones.
Many Australian business systems display dates as DD/MM/YYYY and use a 24-hour clock, but those formatting customs do not alter the UTC-based NTP process. Some Australian routers and internet providers advertise an NTP service, although availability and policies vary. The public Australian pool remains a predictable choice for a personal computer or small office.
Verify and maintain the setup
Check the final state after restarting the computer or reconnecting to the network:
timedatectl show -p Timezone -p NTP -p NTPSynchronized
timedatectl timesync-status
sudo ntpq -p
The ntpq command applies to a dedicated NTPsec or NTP installation; the timesync-status command applies to systemd-timesyncd. With a dedicated daemon, timedatectl may show the built-in NTP service as inactive even though the system clock is synchronised. The kernel status and peer query then provide the useful confirmation.
If synchronisation fails, inspect the relevant service log with sudo journalctl -u systemd-timesyncd -b --no-pager or sudo journalctl -u ntpsec -b --no-pager. Check outbound UDP port 123, DNS resolution for au.pool.ntp.org, and any firewall or VPN configuration. A laptop should normally correct itself after waking from sleep, but waiting briefly for the first network response is normal.
| Feature | Built-in systemd-timesyncd | Dedicated NTPsec or NTP |
|---|---|---|
| Package | Usually installed already | Install ntpsec on current releases or ntp on older releases |
| Main configuration | /etc/systemd/timesyncd.conf |
/etc/ntpsec.conf or /etc/ntp.conf |
| Service control | systemctl enable --now systemd-timesyncd |
systemctl enable --now ntpsec or ntp |
| Australian server | NTP=au.pool.ntp.org |
pool au.pool.ntp.org iburst |
| Connection details | Shown by timedatectl timesync-status |
Shown by ntpq -p |
| Best suited to | Most elementary OS desktops | Detailed peer management and conventional NTP administration |
The practical takeaway is to use systemd-timesyncd for a typical elementary OS desktop, choose the correct Australian IANA time zone, and confirm NTPSynchronized=yes after a restart or network change. That small check prevents the operating system from silently drifting away from the time used by the wider network.