Unable to synchronize system time, Pi-hole not working

[DanSchaper]

@thofra01

Maybe I can run a NTP server on my Pi and have my router as a NTP client? Seems like a stretch but might this resolve the issue? At least the time between both devices should be in sync.

That won't work.

This thread is littered with tangents that muddy the waters so lets start again.

Raspberry Pi devices don't have a Real Time Clock onboard. So they use an application called fakehwclock to fake that facility. It writes a file with the current time when you gracefully shut down the Pi. When it starts up again it reads that file and uses that time as the start time until it can reach a way/process to update the current time (NTP). If you pull the power on the system or crash out then that file is not written and the default time sets back to what is called The Epoch (that 1970s date you often see.)

So, solutions are:

• Spend $5 and attach an RTC module.
• Use NTP servers that can be reached via IP address and don't need DNS resolution to access.
• Set the router to be an NTP server (some have that capability) and configure the Pi to use that as the NTP server.

@thofra01

;versions.pi-hole.net.          IN      A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Feb 23 00:18:52 CET 2022
;; MSG SIZE  rcvd: 49

That looks like it's the right time to me. Does a dig to 1.1.1.1 show an IP address? What port is unbound on and how have you configured Pi-hole to use unbound?