resolution fails when the date of the server is more than 2 days late

dy1977 at dy1977 at
Mon Mar 2 06:59:36 UTC 2020


I am running unbound on SBC cards (Raspberry Pi, Tinker board, Rock64). 
These cards don't have a hardware clock. They are set to resolve to so that the local processes use Unbound for DNS requests. 
Everything fine here.

But when I don't have used a card for more than 1 or 2 days (I didn't 
test the exact threshold), when I start one, I get in a vicious cycle :

The clock is 2 days or more late
All DNS resolutions fail because of this difference calls fail
The clock is not updated
All DNS resolutions fail
And so on...

The way out of the cycle is to set the date manually, after that 
everything is fine again. But the user is not expected to do that in a 
linux command line.

Is there a way to prevent this behaviour from unbound, and get at least resolved when there is a serious clock drift ?

I could do that by setting the ip address of somewhere, but if 
this ip address changes one day, the system will fail again, so I don't 
like it.

There is a ticket here about this question :

If the answer is not obvious, I will provide more details about unbound 
answers in this situation.



More information about the Unbound-users mailing list