Bug#898530: reducing timesync errors

積丹尼 Dan Jacobson jidanni at jidanni.org
Sun May 13 06:47:25 BST 2018


Package: systemd
Version: 238-4
Severity: minor

Upon connecting to the Internet one sees

(1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC, downgrading to non-DNSSEC mode.
(2) systemd-resolved[482]: DNSSEC validation failed for question ntp.org IN SOA: failed-auxiliary
systemd-resolved[482]: DNSSEC validation failed for question pool.ntp.org IN DS: failed-auxiliary
systemd-resolved[482]: DNSSEC validation failed for question 0.debian.pool.ntp.org IN DS: failed-auxiliary
systemd-resolved[482]: DNSSEC validation failed for question 0.debian.pool.ntp.org IN SOA: failed-auxiliary
systemd-resolved[482]: DNSSEC validation failed for question 0.debian.pool.ntp.org IN A: failed-auxiliary
(3)systemd-timesyncd[483]: Timed out waiting for reply from 61.216.153.107:123 (0.debian.pool.ntp.org).
(4)systemd-timesyncd[483]: Synchronized to time server 35.201.155.83:123 (0.debian.pool.ntp.org).

Well perhaps all the messages at (2) could be avoided as due to (1) we
know not to attempt them.

Also maybe some better servers should be the defaults, so they don't
time out at (3).



More information about the Pkg-systemd-maintainers mailing list