NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one server name or address into a device, and never query more than once every 4 seconds. It strongly encourages moving from the old TIME and DAYTIME protocols to NTP.
\nNIST’s Internet Time Service page says NIST operates several stratum-1 network time servers whose time is directly linked to UTC(NIST), the official NIST time, and that other sources of time are not monitored or certified by NIST. It says most operating systems can automatically synchronize their clocks periodically by querying an NTP server.
\nNIST’s time server list says the global name time.nist.gov resolves to all of its servers in a round-robin sequence to equalize load, that it is bad practice to hard-code a particular server name or address into a device so it cannot be changed later, and that software must never query a server more often than once every 4 seconds, with faster systems refused service. It strongly encourages users of the TIME protocol on TCP port 37 and the DAYTIME protocol on TCP port 13 to upgrade to NTP, and lists separate servers that answer only authenticated NTP requests from registered users.
\nNIST also says its servers add a leap second by repeating 23:59:59, which makes time tags in that second ambiguous and can make it difficult to establish the order of events near a leap second.
\nUse this for any system whose logs or recordings may need to be correlated or used as evidence. Device time settings vary by manufacturer; confirm each device’s NTP options and time zone handling.
\nDSE recommends syncing every security device to an internal NTP source that is itself synced to a trusted reference, so video, access and alarm logs agree to the second. Configure time servers by name where devices allow it, keep polling intervals well above NIST’s 4-second floor, block the old TIME and DAYTIME protocols at the firewall, and alert on devices that drift.
\nEach quarter, compare timestamps from a camera, recorder, door controller and server against the reference clock, record any offset, and correct devices that drift beyond the tolerance set for investigations.
\nNIST — Internet Time Service (ITS). NIST — Internet Time Servers. Reviewed October 19, 2026.
", "content_text": "NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one server name or address into a device, and never query more than once every 4 seconds. It strongly encourages moving from the old TIME and DAYTIME protocols to NTP.\nSource facts\nNIST’s Internet Time Service page says NIST operates several stratum-1 network time servers whose time is directly linked to UTC(NIST), the official NIST time, and that other sources of time are not monitored or certified by NIST. It says most operating systems can automatically synchronize their clocks periodically by querying an NTP server.\nNIST’s time server list says the global name time.nist.gov resolves to all of its servers in a round-robin sequence to equalize load, that it is bad practice to hard-code a particular server name or address into a device so it cannot be changed later, and that software must never query a server more often than once every 4 seconds, with faster systems refused service. It strongly encourages users of the TIME protocol on TCP port 37 and the DAYTIME protocol on TCP port 13 to upgrade to NTP, and lists separate servers that answer only authenticated NTP requests from registered users.\nNIST also says its servers add a leap second by repeating 23:59:59, which makes time tags in that second ambiguous and can make it difficult to establish the order of events near a leap second.\nApplicability\nUse this for any system whose logs or recordings may need to be correlated or used as evidence. Device time settings vary by manufacturer; confirm each device’s NTP options and time zone handling.\nDSE recommendation\nDSE recommends syncing every security device to an internal NTP source that is itself synced to a trusted reference, so video, access and alarm logs agree to the second. Configure time servers by name where devices allow it, keep polling intervals well above NIST’s 4-second floor, block the old TIME and DAYTIME protocols at the firewall, and alert on devices that drift.\nVerification\nEach quarter, compare timestamps from a camera, recorder, door controller and server against the reference clock, record any offset, and correct devices that drift beyond the tolerance set for investigations.\nOfficial references\nNIST — Internet Time Service (ITS). NIST — Internet Time Servers. Reviewed October 19, 2026.", "content_markdown": "NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one server name or address into a device, and never query more than once every 4 seconds. It strongly encourages moving from the old TIME and DAYTIME protocols to NTP.\n\n## Source facts\n\nNIST’s [Internet Time Service page](https://www.nist.gov/pml/time-and-frequency-division/time-distribution/internet-time-service-its) says NIST operates several stratum-1 network time servers whose time is directly linked to UTC(NIST), the official NIST time, and that other sources of time are not monitored or certified by NIST. It says most operating systems can automatically synchronize their clocks periodically by querying an NTP server.\n\nNIST’s [time server list](https://tf.nist.gov/tf-cgi/servers.cgi) says the global name time.nist.gov resolves to all of its servers in a round-robin sequence to equalize load, that it is bad practice to hard-code a particular server name or address into a device so it cannot be changed later, and that software must never query a server more often than once every 4 seconds, with faster systems refused service. It strongly encourages users of the TIME protocol on TCP port 37 and the DAYTIME protocol on TCP port 13 to upgrade to NTP, and lists separate servers that answer only authenticated NTP requests from registered users.\n\nNIST also says its servers add a leap second by repeating 23:59:59, which makes time tags in that second ambiguous and can make it difficult to establish the order of events near a leap second.\n\n## Applicability\n\nUse this for any system whose logs or recordings may need to be correlated or used as evidence. Device time settings vary by manufacturer; confirm each device’s NTP options and time zone handling.\n\n## DSE recommendation\n\nDSE recommends syncing every security device to an internal NTP source that is itself synced to a trusted reference, so video, access and alarm logs agree to the second. Configure time servers by name where devices allow it, keep polling intervals well above NIST’s 4-second floor, block the old TIME and DAYTIME protocols at the firewall, and alert on devices that drift.\n\n## Verification\n\nEach quarter, compare timestamps from a camera, recorder, door controller and server against the reference clock, record any offset, and correct devices that drift beyond the tolerance set for investigations.\n\n## Official references\n\n[NIST — Internet Time Service (ITS)](https://www.nist.gov/pml/time-and-frequency-division/time-distribution/internet-time-service-its). [NIST — Internet Time Servers](https://tf.nist.gov/tf-cgi/servers.cgi). Reviewed October 19, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/", "url": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-19" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Sync cameras, recorders and door controllers to NTP the way NIST asks: no hard-coded servers and no fast polling", "item": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/#article", "identifier": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/", "url": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/", "headline": "Sync cameras, recorders and door controllers to NTP the way NIST asks: no hard-coded servers and no fast polling", "description": "NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one…", "abstract": "NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one server name or address into a device, and never query more than once every 4 seconds. It strongly encourages moving from the old TIME and DAYTIME protocols to NTP.", "articleBody": "NIST operates stratum-1 time servers linked to UTC(NIST) and asks users to reach them through the round-robin name time.nist.gov, never hard-code one server name or address into a device, and never query more than once every 4 seconds. It strongly encourages moving from the old TIME and DAYTIME protocols to NTP.\nSource facts\nNIST’s Internet Time Service page says NIST operates several stratum-1 network time servers whose time is directly linked to UTC(NIST), the official NIST time, and that other sources of time are not monitored or certified by NIST. It says most operating systems can automatically synchronize their clocks periodically by querying an NTP server.\nNIST’s time server list says the global name time.nist.gov resolves to all of its servers in a round-robin sequence to equalize load, that it is bad practice to hard-code a particular server name or address into a device so it cannot be changed later, and that software must never query a server more often than once every 4 seconds, with faster systems refused service. It strongly encourages users of the TIME protocol on TCP port 37 and the DAYTIME protocol on TCP port 13 to upgrade to NTP, and lists separate servers that answer only authenticated NTP requests from registered users.\nNIST also says its servers add a leap second by repeating 23:59:59, which makes time tags in that second ambiguous and can make it difficult to establish the order of events near a leap second.\nApplicability\nUse this for any system whose logs or recordings may need to be correlated or used as evidence. Device time settings vary by manufacturer; confirm each device’s NTP options and time zone handling.\nDSE recommendation\nDSE recommends syncing every security device to an internal NTP source that is itself synced to a trusted reference, so video, access and alarm logs agree to the second. Configure time servers by name where devices allow it, keep polling intervals well above NIST’s 4-second floor, block the old TIME and DAYTIME protocols at the firewall, and alert on devices that drift.\nVerification\nEach quarter, compare timestamps from a camera, recorder, door controller and server against the reference clock, record any offset, and correct devices that drift beyond the tolerance set for investigations.\nOfficial references\nNIST — Internet Time Service (ITS). NIST — Internet Time Servers. Reviewed October 19, 2026.", "datePublished": "2026-10-19T00:27:42+00:00", "dateModified": "2026-10-19T01:55:06+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/nist-internet-time-service-ntp-cameras-recorders-controllers-time-sync/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Sync cameras, recorders and door controllers to NTP the way NIST asks: no hard-coded servers and no fast polling" }, "articleSection": [ "Networks & Infrastructure", "Video Surveillance" ], "keywords": [ "Networks & Infrastructure", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 389, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "NIST — Internet Time Service (ITS)", "url": "https://www.nist.gov/pml/time-and-frequency-division/time-distribution/internet-time-service-its" } } ] } }