Hacker News new | past | comments | ask | show | jobs | submit login
When it's not DNS, it's probably NTP (apnic.net)
14 points by kryster 45 days ago | hide | past | favorite | 6 comments



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!


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!


That's what you got for NTP using domain name, with DNS over HTTPS.


Discussion of the original source: https://news.ycombinator.com/item?id=39324491


This blog post is short and does not contain any material details. Not sure what to discuss on.


Or it’s DNS preventing your NTP domain from resolving, making it both…

I just had that happen a few weeks ago.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: