• Scrath@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    6 hours ago

    Not OP but a lot of people probably use pi-hole which doesn’t support wildcards for some inane reason

    • qjkxbmwvz@startrek.website
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 hours ago

      I switched to Technitium and I’ve been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they’re queried in parallel, a VPN connection can go down without losing any DNS…maybe this is how pihole would have handled it too though).

      And of course, wildcards supported no problem.

    • Croquette@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      That’s my case. I send every new subdomain to my nginx IP on pi-hole and then use nginx as a reverse proxy

      • Scrath@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        4 hours ago

        That was my exact setup as well until I switched to a different router which supported both custom DNS entries and blocklists, thereby making the pi-hole redundant

        • Croquette@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          19 minutes ago

          I run opnsense, so I need to dump pi-hole. But I don’t have the energy right now to do that.

          Pi-Hole was pretty straightforward at the time and I did not look back since then. Annoying, but easy.