I don't want to be intrusive: maybe ipv6 configuration was incomplete or only link-local (fe80::/10). mmmh, actually, specially with win10 clients a pi-hole protected lan should be fully ipv6 enabled.
Search Criteria
Package Details: pi-hole-server 5.18.3-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/pi-hole-server.git (read-only, click to copy) |
---|---|
Package Base: | pi-hole-server |
Description: | The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server. |
Upstream URL: | https://github.com/pi-hole/pi-hole |
Keywords: | ad block pi-hole |
Licenses: | EUPL-1.2 |
Conflicts: | pi-hole-standalone |
Submitter: | max.bra |
Maintainer: | max.bra (graysky) |
Last Packager: | max.bra |
Votes: | 112 |
Popularity: | 0.146054 |
First Submitted: | 2016-01-13 12:50 (UTC) |
Last Updated: | 2024-08-10 12:32 (UTC) |
Dependencies (18)
- bc (bc-ghAUR)
- bind-tools (bind-developmentAUR, bind-gitAUR, bind)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR)
- iproute2 (iproute2-gitAUR, busybox-coreutilsAUR, iproute2-selinuxAUR)
- jq (jq-gitAUR)
- logrotate (logrotate-gitAUR, logrotate-selinuxAUR)
- lsof (lsof-gitAUR)
- netcat (nmap-netcatAUR, openbsd-netcat-gitAUR, gnu-netcat-svnAUR, gnu-netcat, openbsd-netcat)
- perl (perl-gitAUR)
- pi-hole-ftlAUR
- procps-ng (procps-ng-gitAUR, busybox-coreutilsAUR)
- sudo (fake-sudoAUR, polkit-fakesudoAUR, sudo-gitAUR, doas-sudo-shimAUR, doas-sudo-shim-minimalAUR, sudo-hgAUR, sudo-selinuxAUR, fudo-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- lighttpd (optional) – a secure, fast, compliant and very flexible web-server
- nginx-mainline (nginx-quic-openssl-hgAUR, nginx-quic-libresslAUR) (optional) – lightweight http server
- php-cgi (optional) – CGI and FCGI SAPI for PHP needed only for lighttpd
- php-fpm (optional) – FastCGI process manager for php needed for nginx
- php-sqlite (optional) – sqlite db access for nginx
Required by (2)
- padd-git
- pi-hole-whitelist-git (optional)
Sources (15)
- 01-pihole.conf
- https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-admin-5.21-4.patch
- https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-core-5.18.3-4.patch
- lighttpd.pi-hole.conf
- mimic_basic-install.sh
- mimic_setupVars.conf.sh
- nginx.pi-hole.conf
- pi-hole-gravity.service
- pi-hole-gravity.timer
- pi-hole-logtruncate.service
- pi-hole-logtruncate.timer
- pi-hole-server-admin-5.21.tar.gz
- pi-hole-server-core-5.18.3.tar.gz
- pi-hole.tmpfile
- piholeDebug.sh
Latest Comments
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 82 Next › Last »
max.bra commented on 2021-04-23 19:52 (UTC)
steadybright commented on 2021-04-23 18:28 (UTC) (edited on 2021-04-23 19:22 (UTC) by steadybright)
@max.bra My pi-hole-server instance is running on my Arch Linux server. I have a Raspberry Pi 4B that also runs on Arch Linux (linux-raspberrypi, thanks to @graysky), but I do not run pi-hole on it. Some time ago, I disabled IPv6 on my Arch server because I was receiving incessant messages about connection failures from urbackup (among others) because they were looking to connect on IPv6. Disabling IPv6 fixed that issue, but apparently is causing other problems. It was a band-aid approach, and I suppose I should re-enable IPv6 on the server and just delete the logs more frequently.
max.bra commented on 2021-04-23 16:54 (UTC) (edited on 2021-04-23 17:02 (UTC) by max.bra)
you are welcome, thanks to you.
p.s.: obviously it would have been possible to solve by enabling a full ipv6 on your lan. if you are interested (choosing archlinux instead of a more classic raspberry distribution makes me think of it) would solve all your future problems without any system "hacking".
read: ... a more classic and pihole supported distribution ...
steadybright commented on 2021-04-23 16:43 (UTC)
That resolved it. Thank you again for you help with this--and for maintaining pi-hole-server for Arch!
max.bra commented on 2021-04-23 16:24 (UTC)
yes perfect. your pihole seems to be ok and ipv4 only. assuming your ISP is ipv6 compatible, i suspect that your win10 now relay (at it pleasure and after our tests) on ipv6 dns resolution. can you prioritize ipv4 following this 'https://tinyurl.com/y8pr7bxh' (Solution 1 recommended)?
steadybright commented on 2021-04-23 16:05 (UTC)
@max.bra I haven't used pastebin before, but here's what I think you're looking for: https://pastebin.com/mFgeNrBV
My browsing machine is Windows 10 and I'm using Firefox 88.0 64 bit
max.bra commented on 2021-04-23 15:55 (UTC) (edited on 2021-04-23 15:56 (UTC) by max.bra)
ok, step by step,
please: info about your browsing machine, in your pihole pastebin of 'pihole status' and a pastebin of your /etc/pihole/setupVars.conf
steadybright commented on 2021-04-23 15:52 (UTC) (edited on 2021-04-23 15:55 (UTC) by steadybright)
I just remoted in to another machine on my LAN and tried to navigate to a blocked site. It was blocked. Must be something to do with the machine I'm on physically. Thank you for your help!
steadybright commented on 2021-04-23 15:49 (UTC) (edited on 2021-04-23 15:49 (UTC) by steadybright)
I just re-confirmed 1. My router is using my pi-hole server for DNS, with no backup DNS server 2. Rebooted my router 3. Confirmed my local machine (from which I'm browsing) has my router as its DNS server, with no backup DNS server configured 4. Cleared my browser cache on my browsing machine 5. Rebooted my browsing machine 6. Confirmed that pi-hole-server is running, enabled, and without any errors. 7. Rebooted my pi-hole-server machine
Confirmed that nothing is being filtered. I don't know enough about DNS to know if there's a ghost somewhere causing this issue, but I've tried to run to ground all the obvious problems.
max.bra commented on 2021-04-23 15:27 (UTC)
@steadybright or maybe your desktop is on windows? ipconfig /flushdns?
Pinned Comments
max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (UTC) by max.bra)
ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.
First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.