Pi-hole 2.5.3 Released With More Choices!

We’ve made a few changes in this release, details of which can be seen on the changelog wiki pages for pi-hole and for the web admin page.

If you want to use the new features, then as always just run the installer again.  This is the best way to do it until we get our update mechanism working.

Several changes of note:

  • We’ve added even more choices for upstream DNS servers to the install script, including the ability to define your own!

dns-selection

  • We’ve made a few tweaks to the default ad-lists. This means that by default we are blocking less domains that the last release, but hopefully that means less false-positives. A couple of lists we added in the last release blacklisted some legitimate sites, including CDNs for jquery and Windows update… If you still want to include these lists, then you can follow the instructions here in order to re-enable them.

 

  • The web admin page has received a major overhaul, which includes some fancy new graphs and charts to better inform you of what the pi-hole is doing.

pihole-stats-dashboard-noberry

 

 

24 Replies to “Pi-hole 2.5.3 Released With More Choices!”

  1. Hey, after the update, i dont find the web admin page on ip/pihole/index.php again. is there a new link?! regard from swiss. hoerg

    I fixed the problem, the updatescript goes to ip/admin not to pihole, so i changed the link.

    1. Glad you found it OK! You must have been running a fairly old version for it to still be in ip/pihole/index.php. How do you like the new changes?

  2. Love this update! The dashboard is really cool and the DNS options are terrific. Thanks again for the great work. I can see how the Github move has really accelerated the great work started by Jacob!

    1. Thanks! We are pretty excited, too. There has been a lot of support from our users and it keeps us motivated.

  3. I updatet my privat now with the Black and Whitelist and a List Update Link.
    It work really good. I love that Blocker, thanks Jacob

          1. If the update script dont work, you have to edit the file sudoers wich you will find in /etc/
            you have to add
            www-data ALL=(ALL) NOPASSWD: ALL

            But with this edit you will open the root rights for www-data, so if you have the Pi-hole in the Internet with DDNS not only in the LAN, you should not do that. I am still looking for another workaround.

          2. Instead of having ALL at the end of the sudoers line you can specify specific commands. This eliminates the attack surface.

          3. If the update script dont work, you have to edit the file sudoers wich you will find in /etc/
            you have to add
            www-data ALL=(ALL) NOPASSWD: ALL

            But with this edit you will open the root rights for www-data, so if you have the Pi-hole in the Internet with DDNS not only in the LAN, you should not do that. I am still looking for another workaround.

          4. Please note that that file is not made by the Pi-hole team as we are still working on developing the whitelist/blacklist feature to avoid having to use sudo

          5. Please note that that file is not made by the Pi-hole team as we are still working on developing the whitelist/blacklist feature to avoid having to use sudo

  4. Thanks for the update !

    What do you guys suggest on the memory split option at the advanced options with sudo raspi-config ?

    1. If you are running it as a server and configure everything over ssh, zero. Pi-hole runs best on Raspbian Jessie Lit.

    2. If you are running it as a server and configure everything over ssh, zero. Pi-hole runs best on Raspbian Jessie Lit.

  5. I cloned the AdminLTE git and then copied contents with “cp -r * /var/www/pihole”.

    Everything works but I get stuff like “query[A]: 3515” under Query Types and Top Clients only lists gateway and local, is that normal?

    1. query[A] is IPv4 requests so that’s completely normal; you would see [AAAA] for IPv6 traffic. Top clients are the devices that are using Pi-hole so you must only have two devices using it.

    2. query[A] is IPv4 requests so that’s completely normal; you would see [AAAA] for IPv6 traffic. Top clients are the devices that are using Pi-hole so you must only have two devices using it.

    1. Haha I actually started making a little script that would send a tweet to the advertisers telling them I blocked on of their ads…Kind of a side-project right now.

Leave a Reply