Lee <[email protected]> writes: > On Sat, Sep 27, 2025 at 7:50 AM Richmond wrote: >> >> Today I had no DNS. I have DNSSEC configured using DNS trigger and >> uninstalling that package restored connectivity. Then re-installing >> seems OK, maybe until next reboot? But I don't know why it happened, >> maybe because of a new kernel recently? > > Maybe your time was off? > > I helped my wife put Debian on her laptop & firefox didn't work until > we set the correct time on the laptop > (everything being https, everything fails if the laptop time is hours > or days in the past) > > I'm tempted to install ntpd because I know how to set the time at > bootup -- systemd is a mess. I see why people rant about how fucked > up systemd is. setting the time at boot up is a solved problem.. or > at least it was back when using ntpd. I haven't figured out the magic > incantation to get the correct time set automatically when systemd is > controlling the time :( >
Aha! This is a lightbulb moment for me. I recently installed a new Debian 13 in a new partition, and the system clock was wrong. I thought this was because I had installed a very minimal system and had not included ntp, so I got errors in aptitude saying things were not yet available. But now I see these problems are probably due to the laptop having no battery in it, and if there is a CMOS or BIOS battery, that's probably gone flat. By installing a minimal system I was able to go from cold boot to browser up and running in 1.5 minutes, whereas normally it takes 3.5 minutes.
