Dear DietPi Developers,
When installing DietPi with Pi-hole and Unbound, the DNS selection prompt can be confusing. Many users, including myself, mistakenly enter the Unbound localhost IP+port, assuming it’s for Pi-hole’s DNS settings. This can cause DNS conflicts, especially with Tailscale, leading to internet outages.
I recently discovered during a clean install that this prompt is for DietPi’s own DNS, not Pi-hole or Unbound. Entering Quad9 DNS here and configuring Pi-hole’s DNS in its web interface resolved my issues. However, the prompt lacks clear guidance, and I suspect others make the same mistake.
Please consider adding a note to clarify that this DNS setting is for the DietPi device itself, not Pi-hole or Unbound, and warn that using the Unbound localhost IP+port may cause conflicts. This small change could save users significant troubleshooting.
Thank you for your consideration.
Can you share the screen you are referring to? Our script doesn’t have a DNS selection screen included. There is one from PiHole installer itself but should not have an effect if you select unbound together. Because we will set PiHole upstream DNS to unbound automatic afterwards.
For months, my internet randomly cuts out. Each time, I fix it by going into Tailscale’s admin console, removing the DietPi device’s Tailscale IP from DNS nameservers, and unchecking “override DNS.” I thought it was a Pi-hole config issue, so I set “accept DNS” and “accept routes” to false on the DietPi device, but no luck. I reinstalled DietPi and Pi-hole, and this time, during the blue-background terminal DNS prompt, I picked Quad9 instead of localhost unbound. After Pi-hole installed, Quad9 wasn’t checked in Pi-hole’s DNS settings, which is why I figured this prompt is meant for the device and not Pihole.
Suddenly, no DNS issues. This led me to believe that the prompt sets the device’s DNS, not Pi-hole’s, causing a loop conflict. A clean installation with this change fixed it, but something feels off.
Although outdated and missing the current localhost option, the screenshot below was scraped from Google images, but it’s literally the same step I’m referencing.
This is not a DietPi setting, it’s a screenshot from PiHole installer. But it will have no effect on anything as we overwrite this with Unbound if selected during installation.
Interesting.
My mistake. Perhaps this issue I’ve experienced stems from Pihole itself.
Feel free to delete this post as it will bring no value and perhaps cause confusion.
