Configure Your NAS As A Reliable Network Time Server
Accurate time is easy to overlook when setting up a NAS, yet it supports authentication, backup schedules, file versions, surveillance recordings and system logs. A few minutes of clock drift can make a failed backup appear successful, break certificate checks or leave security events in the wrong order.
A Synology or QNAP NAS can synchronise with a public time source and then provide Network Time Protocol (NTP) services to computers, cameras, virtual machines and other network equipment. This creates a consistent clock across a home office, small business or larger local network.
The arrangement is especially useful where an internet connection is not perfectly stable. Australian households using NBN connections can experience short outages, while regional properties and workshop networks may rely on wireless broadband. Once the NAS has obtained the correct time, local devices can continue checking against it during a temporary internet interruption.
Time zones do not change the underlying NTP value. NTP uses coordinated universal time (UTC), while your devices display local time according to their own region and daylight-saving rules. That distinction matters in Australia, where Sydney and Melbourne change clocks seasonally but Brisbane, Perth and Darwin do not.
Why Consistent Time Matters On A NAS
A shared time source gives every device on the LAN a common reference. A laptop, IP camera and NAS might otherwise obtain time from different internet servers, producing small differences that become troublesome when logs are compared or automated jobs run close together.
Backup software depends on reliable timestamps when deciding whether a file has changed. Replication tools, snapshots and cloud synchronisation also use dates to identify versions. If a client clock is wrong, an old file may appear newer than the current copy, or a scheduled task may run at an unexpected hour.
Authentication is another important consideration. Kerberos-based services, directory integrations and some single sign-on systems reject requests when the client and server clocks differ beyond an allowed tolerance. TLS certificates and signed software packages can also behave strangely when a device believes it is in the past or future.
A NAS time server is useful for cameras and access-control devices that cannot be configured with several external time sources. It can also make troubleshooting easier: a log from a QNAP, router and Windows workstation is much more valuable when all three use the same clock.
Prepare The Network Before Enabling NTP
The NAS needs a dependable network address. Set a DHCP reservation in the router or assign a static address through the NAS network settings, ensuring that the address is outside the router’s automatic DHCP range. Record the address and hostname so clients continue to find the same server after a reboot.
Before enabling local time services, configure the NAS itself to synchronise with an upstream source. Australian users can select an Australian NTP pool, such as au.pool.ntp.org, or use a trusted provider recommended by their internet service provider. The NAS should normally use several upstream servers rather than relying on one hostname or one physical machine.
Useful preparation checks include:
- Confirming the NAS has the correct gateway and DNS servers
- Reserving a fixed LAN address for the NAS
- Checking that outbound UDP port 123 is allowed
- Updating DSM, QTS or QuTS hero before changing services
- Verifying that the router does not block local NTP traffic
- Recording the NAS address for client configuration
NTP uses UDP port 123. A typical home network does not need port forwarding from the internet to the NAS, and exposing an NTP service publicly can create abuse and security problems. Keep the service limited to trusted interfaces or VLANs wherever the NAS allows that level of control.
Set the correct regional time zone on the NAS as well. Choose an Australian city matching the site, such as Australia/Sydney, Australia/Brisbane or Australia/Perth. The NTP protocol will still operate in UTC, but the NAS interface, task schedules and displayed logs will use the selected local rule.
Enable The Service On Synology DSM
In DSM, open Control Panel and locate Regional Options or the Time settings, depending on the DSM release. Select manual configuration or synchronisation with an internet time server, choose an appropriate Australian source, and run a synchronisation. Check that the displayed status shows a successful update rather than simply saving the server name.
Synology models and DSM versions do not always present the server option in the same place. On supported systems, the NTP server function may be enabled through the Synology package catalogue or a dedicated time-service setting. Install only the official package or feature supplied for that DSM version, then enable NTP service for the LAN interface.
After activation, configure a test computer to use the NAS address as its preferred time server. On Windows, the setting is available under Date & time or through the w32tm command. On Linux, timedatectl can select the NAS, while macOS users can enter the address under Date & Time settings. Allow the operating system’s own time synchronisation service to make the change rather than manually setting the clock and leaving automatic updates disabled.
Some Synology installations use firewall rules that block services even when the package is running. Open Control Panel, Security and Firewall, then permit NTP traffic from the relevant local subnet. Do not allow broad internet access unless there is a clear, well-managed requirement. If the NAS is on a separate management VLAN, add only the network ranges that need time synchronisation.
Configure NTP On QNAP QTS Or QuTS Hero
On QNAP systems, open Control Panel and find the Date and Time section. Select automatic synchronisation with an internet time server, enter a suitable upstream hostname, and apply the setting. Use the NAS status display to confirm that the clock has synchronised and that the selected time zone matches the installation.
The NTP server option may be located under network services, system administration or an installed QNAP application, depending on whether the device runs QTS or QuTS hero. Enable the service only after the NAS has a reliable upstream clock. If the interface offers listening interfaces or access controls, select the LAN or service VLAN rather than every available interface.
For QNAP clients, the important values are the NAS hostname or fixed IP address and UDP port 123. A Windows domain controller, managed switch, Wi-Fi access point or surveillance recorder can use the NAS as a preferred or secondary source. Keep a more authoritative upstream source configured on the network’s primary infrastructure when practical, particularly in a business environment.
A sensible QNAP configuration normally includes these checks:
- Confirming the NAS synchronises after a restart
- Testing UDP 123 from a client on each required VLAN
- Reviewing QTS or QuTS hero firewall permissions
- Limiting NTP access to trusted internal subnets
- Checking that virtual machines use the intended host or LAN source
- Comparing the NAS clock with an independent Australian time source
Small Australian offices often run a NAS beside the router in a comms cupboard, with staff working from home in the afternoon or “arvo”. Remote users should generally synchronise with their own internet-connected systems or VPN infrastructure, not with an NTP service exposed directly from the office NAS.
Test Accuracy And Keep The Service Healthy
Start with one client and compare its time against the NAS, then test devices that matter most, such as backup servers, cameras and directory services. On Linux, chronyc sources or timedatectl timesync-status can show the selected source. On Windows, w32tm /query /status and w32tm /stripchart /computer:NAS-IP can help identify offset and reachability.
A small offset is normal while a client adjusts its clock. A persistent error, failed reachability test or rapidly changing offset suggests a configuration problem. Check DNS resolution, firewall rules, VLAN routing, the NAS gateway and whether another policy is overriding the client’s time-server setting.
Scheduled jobs deserve special attention around daylight-saving changes. A task set for 2:30 am in Melbourne may be affected when clocks move forward or back, whereas a Brisbane schedule follows a different rule. For critical backups, document whether the job is based on local time or UTC and inspect the next run after a regional time change.
Use the following maintenance routine to keep the setup dependable:
- Review NAS time status after firmware upgrades
- Check logs for failed upstream synchronisation
- Confirm clients still point to the correct NAS address
- Re-test after changing VLANs, routers or firewall policies
- Keep at least one alternate upstream time source
- Monitor backup and surveillance timestamps for anomalies
The NAS should not become the only source of truth without a recovery plan. If it is powered down for maintenance, clients need a secondary NTP source or another internal server. UPS protection helps keep time services available during brief power events, which is useful during summer storms, regional outages and unstable premises power.
For a home user, one NAS and one upstream pool may be sufficient. A business handling financial records, customer data or compliance evidence should consider two internal time sources, documented configuration, restricted NTP access and regular checks against a trusted external reference.
Apply the settings during a quiet maintenance window, synchronise the NAS first, then move a small number of clients to its address and verify their logs. Once the results are consistent, extend the configuration to backups, cameras, workstations and network equipment. A few careful checks will give the whole Australian home or office network a dependable shared clock without exposing the NAS to the public internet.