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.

  • Matt The Horwood@lemmy.horwood.cloud
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    6 hours ago

    If you run a single DNS server, you will always have downtime when it’s restarted.

    The only way to mitigate that, is to run 2 DNS servers.

    I setup my network to use pihole as the first DNS and the router as the second, most of the time pihole is used. Unless it’s down

    • natch@lemmy.today
      link
      fedilink
      English
      arrow-up
      7
      ·
      5 hours ago

      Just be sure that the second server in the list is also a black hole. If you don’t, all black holed requests will fallback to the second DNS… which, if it doesn’t also black hole them, will wind up serving you ads and defeating the point!

      Personally I find a single Pi is just fine for DNS. It only takes like 10 seconds to reboot. Less, if you use M.2 storage via a HAT or boot from USB! That’s pretty fine downtime. But if you’re afraid you’ll knock over the network and get yelled at by your family or housemates, best to use a backup :)

    • tofu@lemmy.nocturnal.garden
      link
      fedilink
      English
      arrow-up
      5
      ·
      6 hours ago

      How do you set up clients so they will always use the first one? I thought if a client knows 2 servers they will switch between them.

      I plan to add a second Pihole at some point and keep them synced