It looks like my timing issue has been resolved; below is the ntp.conf file from etc/ntpsec/ in the event it may be of use to someone else that wants to use the U.S. based time.nist.gov servers. I am still wondering about the 'restrict nopeer ignored' warning, but am not going to lose sleep over it just yet.
It took some reading, installing ntp, and some experimenting but it was worth the effort.
It took some reading, installing ntp, and some experimenting but it was worth the effort.
Code:
# /etc/ntpsec/ntp.conf, configuration for ntpd; see ntp.conf(5) for helpdriftfile /var/lib/ntpsec/ntp.driftleapfile /usr/share/zoneinfo/leap-seconds.list# To enable Network Time Security support as a server, obtain a certificate# (e.g. with Let's Encrypt), configure the paths below, and uncomment:# nts cert CERT_FILE# nts key KEY_FILE# nts enable# You must create /var/log/ntpsec (owned by ntpsec:ntpsec) to enable logging.#statsdir /var/log/ntpsec/#statistics loopstats peerstats clockstats#filegen loopstats file loopstats type day enable#filegen peerstats file peerstats type day enable#filegen clockstats file clockstats type day enable# This should be maxclock 7, but the pool entries count towards maxclock.tos maxclock 11# Comment this out if you have a refclock and want it to be able to discipline# the clock by itself (e.g. if the system is not connected to the network).tos minclock 4 minsane 3# Specify one or more NTP servers.# Public NTP servers supporting Network Time Security:# server time.cloudflare.com nts# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will# pick a different set every time it starts up. Please consider joining the# pool: <https://www.pool.ntp.org/join.html>##pool time.nist.gov iburst prefer###pool 0.debian.pool.ntp.org iburst#pool 1.debian.pool.ntp.org iburst#pool 2.debian.pool.ntp.org iburst#pool 3.debian.pool.ntp.org iburst# Access control configuration; see /usr/share/doc/ntpsec-doc/html/accopt.html# for details.## Note that "restrict" applies to both servers and clients, so a configuration# that might be intended to block requests from certain clients could also end# up blocking replies from your own upstream servers.# By default, exchange time with everybody, but don't allow configuration.restrict default kod nomodify nopeer noquery limited# Local users may interrogate the ntp server more closely.restrict 127.0.0.1restrict ::1Statistics: Posted by Augie77 — 2024-04-09 03:11