# NTP Time Server Node

**URL:** <https://discourse.nodered.org/t/ntp-time-server-node/76984>\
**Category:** General\
**Created:** [27 March 2023 11:38 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984 "2023-03-27T11:38:10Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![craigcurtin](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@craigcurtin](https://discourse.nodered.org/u/craigcurtin)\
**Post date:** [28 March 2023 21:57 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/21 "2023-03-28T21:57:39Z")

</div>

Dont delete it BUT put a very strong recommendation that people think about the greater good and do not spam the public NTP servers.

I have not looked at your node but presumably you can direct it to look at any NTP server - if so it would be worthwhile telling people to try and only use their own internal NTP servers if they are going to hit NTP sources heavily (but as Julian says i can not understand why you would either)

Craig

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [29 March 2023 00:32 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/22 "2023-03-29T00:32:58Z")

</div>

Most, and every public NTP server I've ever looked at limit requests from an IP address as well. So if you hit the server too often they will block your IP anyway. Don't recall what that time limit is but easy to find out.

---

<div class="post-metadata">

**Author:** ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)\
**Post date:** [29 March 2023 15:46 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/23 "2023-03-29T15:46:23Z")

</div>

Hi,  
Thank you for the hints.  
I changed the default cycle time to 1 minute in the node.  
I removed queries in ms.  
I have also added a note to blocking the IP  
for very short queries to the node description.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [29 March 2023 19:38 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/24 "2023-03-29T19:38:34Z")

</div>

Looked up the time for server requests and they state NEVER request time more than every four seconds so I'd say a minute is comfortably outside that spec.

---

<div class="post-metadata">

**Author:** ![damica51](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@damica51](https://discourse.nodered.org/u/damica51)\
**Post date:** [29 March 2023 20:42 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/25 "2023-03-29T20:42:54Z")

</div>

I want to chime in here, not everyone understand ever single use of these (2) nodes, I'm sure there are applications (just like mine) that has a need for such a node!

PLEASE DO NOT DELETE\>

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [28 May 2023 20:43 UTC](https://discourse.nodered.org/t/ntp-time-server-node/76984/26 "2023-05-28T20:43:03Z")

</div>

Closed on 28 May 2023 20:43 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/ntp-time-server-node/76984.md?page=1)