Jump to content

FDM80

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

2 Neutral

About FDM80

  • Rank
    Newbie
  1. You should check out this website. Ad blocking, telemetry, malicious sites, etc. that you can add to your pihole. https://firebog.net/ For starters, I'd recommend the below list which is all the ones on the website with a check mark next to them. It is the list that is least likely to interfere with normal browsing habits (ie: not as aggressive as some of the other lists) https://v.firebog.net/hosts/lists.php?type=tick
  2. We are waiting for the official docker container to be updated. Once that happens, we will have caught up with the rest of the group. https://hub.docker.com/r/pihole/pihole/ If you look at the Tags tab, you can see the one we normally use (latest) is 7 days old and there is a dev version that is 3 days old.
  3. I think the --dns argument in combination with the network type set to Custom: br0 doesn't play nice together. Just in testing, when I set the network type to Host, start the container, and check the log, the DNS sets properly to 127.0.0.1. I didn't try Bridge mode because there is a conflict with port 80 and I don't feel like messing with those settings right now but that is something else to look into. I don't have enough knowledge of unraid and how the container networking works to offer a solution. All I can do is point to the behavior I notice and hope that someone with more experience can shed some light. I get those other messages in my log as well but I don't see what negative repercussions there are from that so I personally am not concerned about those. At the end of the day, the 127.0.0.1 issue results in the container failing to resolve DHCP hostnames so you just see IP addresses in the dashboard. Mainly a cosmetic issue.
  4. This probably has something to do with the "nameserver 127.0.0.11" behavior. https://github.com/pi-hole/docker-pi-hole/issues/410
  5. I've never tried to change the log storage length so I'm not an expert. I think you can edit the "pihole-FTL.conf" file in the appdata folder to set when things get flushed. See link below. You should look at the "MAXLOGAGE" setting and / or the "MAXDBDAYS" from the looks of things. https://discourse.pi-hole.net/t/how-to-set-a-limit-to-log-file-length-to-maximum-used-log-file-space/6482 My understanding is that the logs are short term storage (default 24 hours stored in the image) and the database is long term storage (default 365 days stored in the appdata folder outside the image). As for if you are concerned about the logs being stored inside the container image, you could maybe do the following to move the log storage out of the image.
  6. Looks like Pi-hole v4 just came out. https://pi-hole.net/2018/08/06/pi-hole-v4-0-released-with-ftldns-improved-blocking-modes-regex-docker-and-more/ It looks like they have brought diginc into the fold and have turned his work into an official docker. I assume the unRaid template will be updated with any necessary changes.