The box itself does not allow the systemd time keeping system to start, due to being in a container. I assume proxmox is working as the time keeper for the containers.
Proxmox does sync time, and the time zone is set correctly on both hypervisor and container. So short answer is that running 'date' in the debian container returns the correct time and time zone. On Thu, 16 Jan. 2020, 17:05 Erik Dobák, <erik.do...@gmail.com> wrote: > > > On Thu, 16 Jan 2020 at 04:22, Brendan Konings via unbound-users < > unbound-users@lists.nlnetlabs.nl> wrote: > >> Hello All, >> >> I have set up a Debian 10 container in Proxmox, for the purpose of >> running pi-hole. This works fine. >> >> I installed Unbound from apt, and configured as per these instructions: >> https://docs.pi-hole.net/guides/unbound >> I reach the point of testing Unbound (before plugging in to pihole, so >> effectively a stand alone installation at this point), but the testing >> fails. Any dig sent to @127.0.0.1 -p 5353 (Unbound) returns SERVFAIL. >> >> I have tried working out the issue with the pihole team, but my >> configuration matches other working systems, so something seems to be going >> wrong with my Unbound installation, or the OS environment it is running in. >> >> Has anyone had issues running Unbound in a CT/Proxmox? >> >> Kind Regards, >> Brendan J Konings, BEng(Electronics)(Hons), BCompSc >> >> https://keys.mailvelope.com/pks/lookup?op=get&search=0x9531F80123B4E094 >> >> _______________________________________________ >> unbound-users mailing list >> unbound-users@lists.nlnetlabs.nl >> https://lists.nlnetlabs.nl/mailman/listinfo/unbound-users > > is yout time corrects on that box? > > E >
_______________________________________________ unbound-users mailing list unbound-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/unbound-users
