Using NTP server
ntp1.barsik.space
(Russia, Moscow, stratum 2)
ntp2.barsik.space
(Russia, Moscow, stratum 2)
Network Time Protocol (NTP) is a network protocol for synchronizing the internal clock of a computer using variable latency networks based on packet switching - in the case of a layman, with a server located on the Internet.
Time is represented in the NTP system as a 64-bit number, consisting of a 32-bit counter of seconds and a 32-bit counter of fractions of a second, allowing the transmission of time in the range of 232 seconds, with a theoretical precision of 2-32 seconds. Since the NTP timeline repeats every 232 seconds (136 years), the recipient must at least roughly know the current time (with 68 years accuracy). It should also be borne in mind that the time is counted from midnight on January 1, 1900, and not from 1970, so almost 70 years must be subtracted from the NTP time (taking into account leap years) in order to correctly match the time with Windows or Unix systems.
How it works
NTP servers operate in a hierarchical network, each level of the hierarchy is called a tier (stratum). Tier 0 is represented by a reference clock. The reference is taken from the GPS (Global Positioning System) or ACTS (Automated Computer Time Service) signal. At tier zero, NTP servers do not work.
Tier 1 NTP servers receive time data from a master clock. Tier 2 NTP servers synchronize with Tier 1 servers. There can be up to 15 tiers in total.
NTP servers and NTP clients receive their time data from Tier 1 servers, although in practice NTP clients are better off not! It's better to set up a local NTP server that your clients will use to get time information. That is why the number of NTP servers must grow. Our project gives the world an NTP server for unraveling and optimizing the operation of networks. The more NTP servers in the world and the more geographically distributed they are, the better.
The hierarchical structure of the NTP protocol is fault-tolerant and redundant. Let's look at an example of how it works. The two Tier 2 NTP servers synchronize with six different Tier 1 servers, each over an independent link. Internal nodes are synchronized with internal NTP servers. The two Tier 2 NTP servers coordinate time with each other. In the event of a link failure with the Tier 1 server or one of the Tier 2 servers, the redundant Tier 2 server takes over the synchronization process.
Likewise, nodes and devices in Tier 3 can use any of the servers in Tier 2. More importantly, having a redundant network of NTP servers ensures that the time servers are always available. Synchronized with multiple time servers, NTP uses data from all sources to calculate the most accurate time.
It's worth noting that NTP does not set the time in its purest form. It adjusts the local clock using a time offset, the difference between the time on the NTP server and the local clock. NTP servers and clients adjust their clocks, synchronizing with the current time gradually or simultaneously.
Configure Internet Time (NTP) options in Windows 10 fe
1. Open Control Panel.
2. Go to the following section: Control Panel\Clock, Language, and Region.
3. Click the icon Date and Time:The following window will appear
4. There, switch to the tab named Internet Time. To adjust available settings, you need to click the button "Change settings...".
5. Once you click it, you will be able to enable NTP and specify a custom time server if required - enter "ntp1.barsik.space" and click OK.
|
