Pihole + adlists + dyndns vs myfritz.net - connection refused

On my fritz.nas I do have serveral blocking lists, I created a sharing link with myfritz.net,
so with myfritz.net + sharing link pihole can fetch the lists.

When I am changing my myfritz to my dyndns address pihole is getting "connection refused" while pulling the shared lists.

I already added my dyndns address to the rebind allow list in my fritzbox

Any ideas?

What is the goal you're trying to archive? Maybe there is another way to do it...

Wanted to change djejeje7337336.myfritz.net to myname.dyndns.com, cause myfritz address will change when fritzbox will exchanged cause dyndns will stay longer and be stable

I understood why you wanted to switch to a dyndns, but still I'm not sure what your end goal is?

Do you want to share adlists you host locally on your NAS with other people?

I maintain lists on my NAS and feed pihole and I can share my lists with others

I'm not sure if it's a problem with pihole or if it's a configuration issue with your myfritz/dyndns.

Are you able to access the lists manually, so to rule out that it's releated to pihole?
Your question might be better suited in a Fritz!Box forum.

There are other options to share/maintain lists, maybe this would be something for your case?

I can access lists both ways manually in browser, dyndns and myfritz. I am getting error only while pihole is grabbing lists using myfritz in automated fetching

Are you able to resolve the addresses themselves on the server running Pihole?

Yes can be resolved, fritzbox stating connection refused as per pihole logfile

What is the command pihole is using to fetch lists? In logfile shown as ... retrieving ... ?

pi@ph5:~ $ cat /etc/cron.d/pihole
[..]
# Pi-hole: Update the ad sources once a week on Sunday at a random time in the
#          early morning. Download any updates from the adlists
#          Squash output to log, then splat the log to stdout on error to allow for
#          standard crontab job error handling.
19 3   * * 7   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log

pi@ph5:~ $ pihole -g -h
Usage: pihole -g
Update domains from blocklists specified in adlists.list

Options:
  -f, --force          Force the download of all specified blocklists
  -h, --help           Show this help dialog

Meant behind the pi command pihole -g, curl? Ftp?

Curl

I guess there is no difference between

https://mydyndns.dyndns.com:5577/nas/filelink.lua?id=faasdsdafdsfsasdfdsffds8b77c4a9bb749

and

https://s324d3e465xc3453.myfritz.net:5577/nas/filelink.lua?id=faasdsdafdsfsasdfdsffds8b77c4a9bb749

in dowloading adlist from local NAS - what might cause fritzbox to refuse

Dyndns address causes refuse whereas myfritz will be grabbed

You don't need a public hostname to have Pi-hole access your locally stored blocklists.
Using your local hostname will do, normally.
As you are using fritz.nas, accessing files may require authentication, and this may interfere with downloading. There are ways around this, but they involve removing authentication altogether or providing credentials in plain text directly in the URL.

You may access your custom blocklist file on the Pi-hole itself, either by

a) accessing the Pi-hole's filesystem
Assuming you've stored your blocklist in a file at /home/pi/personalblocklist, add the following URL to Pi-hole's Adlist group management

file:///home/pi/personalblocklist

b) hosting it on Pi-hole's webserver
Assuming you are using Pi-hole's lighttpd, move or copy your personalblocklist to /var/www/html/ and add the following URL to Adlist group management

http://pi.hole/personalblocklist
2 Likes

Thanks a ton, both ways r working perfectly !
So I don't rely on fritz.nas router settings :slightly_smiling_face: