Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Realtime clock solution #21

Closed
ghost opened this issue Oct 4, 2022 · 1 comment
Closed

Update to Realtime clock solution #21

ghost opened this issue Oct 4, 2022 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 4, 2022

i tested this project with a TVbox android,
when i lock the entire network DNS via Pi-hole
After power loss
The Clock servers wont connect before the pi-hole start to work, thanks to unbound.
so Unbound returns SERVFAIL for all queries because time error

to recovery from that i need to
sudo date -s "$(wget -qSO- --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z"

i think the DNS encripted protocol can't run without realtime device....
How we can inprove that, for non Realtime battery Devices?
can we patch it?

@DesktopECHO
Copy link
Owner

DesktopECHO commented Oct 4, 2022

Hi, yes this can be fixed - I will include ntp in the next release.
In the meantime, you can add the fix you suggested to /etc/rc.local and it will run when the instance is started.
(I suggest maybe using 1.1.1.1 if DNS isn't available, and /etc/rc.local runs as root so no need to sudo)

date -s "$(wget -qSO- --max-redirect=0 1.1.1.1 2>&1 | grep Date: | cut -d' ' -f5-8)Z"

@ghost ghost closed this as completed Oct 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant