3 ms·

When it's not DNS, it's probably NTP

• jtbayly 3y ago
  Or it’s DNS preventing your NTP domain from resolving, making it both… I just had that happen a few weeks ago.
• j16sdiz 3y ago
  This blog post is short and does not contain any material details. Not sure what to discuss on.
• drewg123 3y ago
  What's really fun is when you use a custom time protocol over TLS, but the host's clock is so far gone that the TLS cert is not valid. D'oh!
  • j16sdiz 3y ago
    That's what you got for NTP using domain name, with DNS over HTTPS.
  • rajnathani 3y ago
    We noticed this in our custom embedded Linux device (at work), where when we didn't have the time sync with NTP turned on for boot (but rather a cron job at an interval further away from boot time) and that our RTC's coin cell was drained due to a small hardware bug, that at first when our API calls from the device were failing that we thought it was a hardware / software driver (WLAN) issue, but it fortunately turned out to be the innocuous issue of TLS failing due to the system clock being so off!
• deleted 3y ago
  [deleted]
• piotrkaminski 3y ago
  Discussion of the original source: https://news.ycombinator.com/item?id=39324491 https://news.ycombinator.com/item?id=39324491