Currently have nice long docker compose file that hosts my PiHole V6 container (along with a bunch of other containers) however, reason i ask this question is because whenever I go to pull an updated image and recreate the container I experience about 20 minutes of no DNS resolution which to my knowledge is due to the NTP clock being out of sync.

What’s the best way to host a DNS sinkhole/resolver that can mitigate this issue?

Was thinking of utilizing Proxmox & LXC but I suspect I’ll get the same experience.


Update: Turns out PiHole doesn’t support two instances, I got both of them on separate devices also set the 2nd DNS server in my routers WAN & LAN DNS settings which did in fact split DNS between both instances however, I lost access to my routers web-ui, my Traefik instance & reverse proxies died and I lost all internet access.

So, don’t do what I did.

  • @[email protected]
    link
    fedilink
    English
    414 hours ago

    I think something else may be wrong if it breaks for 20 minutes. How long does it take for compose to bring the stack up?

    Also assuming you run ntpd or chrony, it should always keep your clock in sync.

    • @[email protected]OP
      link
      fedilink
      English
      2
      edit-2
      11 hours ago

      I think something else may be wrong if it breaks for 20 minutes.

      When I originally setup my PiHole many, many, many months ago when I was still learning the Docker engine I had little to no issue.

      I don’t know what caused it either being a power-outage or network loss but ever since I’ve been experiencing DNS related issues (I suspect it’s NTP not syncing), some days I’ll wake up before work realizing “oh shit I have no internet access” frantically trying to fix the issue.

      I think i might take the advice of other commenters here and host two PiHole servers on separate devices/stacks, just got to hope my router supports it.