Pi-hole checks NTP now hourly?

Help Community Help
1

The issue I am facing:

Since updating to FTL 6.0.3 Pihole querys NTP servers hourly.

That’s in FTL log:

2025-03-01 22:46:12.487 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-01 22:46:12.488 INFO Time offset: 3.109659e-02 ms (excluded 1 outliers)

2025-03-01 22:46:12.488 INFO Round-trip delay: 1.327848e+01 ms (excluded 1 outliers)

2025-03-01 23:46:12.754 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-01 23:46:12.754 INFO Time offset: -2.664157e-01 ms (excluded 1 outliers)

2025-03-01 23:46:12.754 INFO Round-trip delay: 1.904188e+01 ms (excluded 1 outliers)

2025-03-02 00:46:12.932 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 00:46:12.932 INFO Time offset: -7.754564e-02 ms (excluded 0 outliers)

2025-03-02 00:46:12.932 INFO Round-trip delay: 1.175237e+01 ms (excluded 0 outliers)

2025-03-02 01:46:13.126 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 01:46:13.126 INFO Time offset: -5.304813e-01 ms (excluded 1 outliers)

2025-03-02 01:46:13.126 INFO Round-trip delay: 1.157100e+01 ms (excluded 1 outliers)

2025-03-02 02:46:13.340 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 02:46:13.340 INFO Time offset: -5.060605e-01 ms (excluded 1 outliers)

2025-03-02 02:46:13.340 INFO Round-trip delay: 1.231793e+01 ms (excluded 1 outliers)

2025-03-02 03:46:13.486 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 03:46:13.486 INFO Time offset: -5.389452e-01 ms (excluded 0 outliers)

2025-03-02 03:46:13.486 INFO Round-trip delay: 1.159370e+01 ms (excluded 0 outliers)

2025-03-02 04:17:15.101 INFO Gravity database has been updated, reloading now

2025-03-02 04:17:15.157 INFO Compiled 1 allow and 72 deny regex for 55 clients in 50.9 msec

2025-03-02 04:46:13.662 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 04:46:13.663 INFO Time offset: -1.507146e+00 ms (excluded 1 outliers)

2025-03-02 04:46:13.663 INFO Round-trip delay: 1.291302e+01 ms (excluded 1 outliers)

2025-03-02 05:46:13.875 INFO Received 8/8 valid NTP replies from pool.ntp.org

2025-03-02 05:46:13.875 INFO Time offset: -4.700933e-01 ms (excluded 1 outliers)

2025-03-02 05:46:13.875 INFO Round-trip delay: 1.319817e+01 ms (excluded 1 outliers)
Details about my system:

https://tricorder.pi-hole.net/P8j9fL5i/

What I have changed since installing Pi-hole:

Only pihole -up to latest versions.

2

That is the current standard value it gets shipped with but you can adjust it at any time according to your needs

through webui (Network Time Sync)
https://pi.hole/admin/settings/all
through CLI
sudo pihole-FTL --config ntp.sync.interval 86400

2 Likes
3

As pointed out you can change the poll time but you can also just turn it off if you don't have a need for the ntp server. I have pihole at a shop that uses the NTP server to provide time to local security cameras and other devices that I block internet access to. My home one has it turned off as I have no need for it.

4

What is the issue that this is causing?

5

Well, I understand that this is now standard. But I changed it in the settings and now they are queried every six hours.

All fine for me now.

1 Like
6

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