NTP doesn't work anymore in v2: DNSSEC validation failed

[zehnm]

Description

Time update with NTP doesn't work anymore in the new v2 image with Buildroot 2021.02. The log is full of errors:

Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question . IN DNSKEY: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question com IN DS: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question com IN DNSKEY: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question google.com IN DS: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question google.com IN SOA: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question time4.google.com IN DS: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question time4.google.com IN SOA: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question time4.google.com IN AAAA: signature-expired
Feb 02 16:38:48 yioremote systemd-resolved[142]: [🡕] DNSSEC validation failed for question time4.google.com IN A: signature-expired

How to Reproduce

Steps to reproduce the behavior:

1. Use v2.0.0-rc1 image
2. Run initial configuration
3. See time in UI: doesn't get updates
4. See errors with journalctl -f

Expected behavior

Time is updated with ntp

Your Environment

• Version used: v2.0.0-rc1
• Running on:
  • YIO Remote

Additional context

Similar issue: https://bbs.archlinux.org/viewtopic.php?id=240427

systemd now uses DNSSEC by default with downgrade if the servers don't support it. Default time servers are from Google. They support DNSSEC. Initial boot has a date of Feb 2 which makes DNS requests invalid, because of the timeframe. So the ntp servers cannot be resolved and the time never gets synchronized...

Possible solutions:

• Manually set initial time.
  Bad user experience if the remote is switched off for a while and the time has to be manually set again.
• Use standalone ntp client and disable systemd ntp.
  This might still not work if the server name cannot be resolved.
• Disable DNSSEC in systemd.

[zehnm]

Fixed in v2.0.0-rc2