AFAIK the FritzBox switchs mainly to the faster DNS Server. I tried to use Quad9 with cloudfare as the second DNS server, most of the time cloudfare was the used since it was a bit faster.
I tried that, devices just request to alternate dns when they get nothing from pihole. I use adgh, and ig there is a setting where you can set the answer to blocked stuff, like 0.0.0.0, empty…etc. if you set thay to 0.0.0.0, devices won’t query 2nd dns (i hope) when adgh is up. But it is best to have a 2nd pihole/adgh, i have one on my proxmox and another on a pi, synced with adgh sync Edit: if you don’t have another pi, use nextdns
I’ve set my secondary DNS to cloudflare, and my pihole still blocked ads for me. I assumed the secondary DNS server is used only if the primary can’t be pinged. But i haven’t actually looked into it.
Afaik there is no primary and secondary, you cant tell which one to use. Its best to have 2 piholes, but having 2nd DNS set to nextdns or something like that should be fine if you cant run 2 instances, probably not the best setup tho
Putting Cloudflare as my secondary would allow some requests to get through and then often the device whose requests went to Cloudflare would continue using Cloudflare for a while.
The best solution I found was to run a second Pihole and use it as the secondary.
You can use something like orbital sync to keep them syncronized
Pretty much. Not sure how the router determines which DNS to use, but mine seems to latch onto whichever one serves up results the fastest, which would inevitably be cloudflare direct after the pihole returns enough blocks.
So I use a Raspberry Pi Zero W as a dedicated pihole, and my Pi 4 seedbox acts as its own pihole and as a redundant backup. Then use gravity-sync from the Zero to the 4 to mirror the settings.
Another cool trick is using tailscale to ensure your portable devices always can access your Pihole(s) from anywhere and then setting those server’s tailscale addresses as your DNS servers in tailscale.
This way you can always use your DNS from anywhere, even on cell data or on public networks
I keep a third instance of Pihole running on a VPS and use it as the first DNS server in tailscale so it will resolve a bit faster than my local DNS servers when I’m away from home
Huh, I’ll definitely look into that. Both times I tried to route external pihole access, somehow other mystery services found it and it slowed to a crawl from getting absolutely pounded by requests not from me. Thanks for that tip!
Nice! Would you mind sharing the configuration for permanently mounting? I tried it in the past but I never really could get it to work right consistently.
I’ll look up the exact info when I get home and provide links if I can find them again.
The summary is that I had to add a line to /etc/fstab with the ip and folder route of the nas drive and folder, then the mount point in linux, the file system type for the mount, options that give login creds/group id + establish permissions I want to apply to the mount, and an option that keeps the drive from trying to mount until my network is connected.
Finally, for that last option to work, I had to enable a process that I forget the name of. I think it was in systemd, but I was able to initiate it from the command line.
Since I don’t know your level of expertise, I’ll go step by step. Forgive me if you already know how to do some of this.
In terminal, type “sudo nano /etc/fstab” (without quotes). This brings up a file where you can add the mount point so it mounts at boot and set options for the mount. Go to the end of the file and enter a line like the following, substituting your info in the appropriate places:
//[static ip for nas]/[top level folder on nas you want to mount] /[mount point in Linux] [file system type for mount] [mount options, nas login credentials, permissions] 0 0
Mine looks like this: //192.168.1.0/Media /mnt/Media cifs _netdev,user=anonymouse,password=*****,uid=1000,file_mode=0777,dir_mode=0777 0 0
The “_netdev” option is the one that delays the mount until after your network is up. The “file_mode” & “dir_mode” set the mount permissions. There is info out there showing how to insert a reference to a credentials file instead of placing them in fstab in plain text, but I didn’t bother since I have my computer and user profile pretty well locked down.
To get _netdev to work, I had to enter the following in terminal (without quotes): “sudo systemctl enable systemd-networkd-wait-online”.
I couldn’t find all the sites I visited while setting this up, but here are a few:
I don’t know much about the snap but you can use docker compose to stand up a deployment pretty quickly. If you aren’t super confident you could use Nextcloud AIO
You aren’t giving us enough information to even speculate the answer. Are these Enterprise grade servers in a datacenter? Are these home made servers with consumer or low grade hardware you’re calling servers? Are they in the same datacenter or do they go out to the Internet? What exists between the hops on the network? Is the latency consistent? What is the quality of both sides of the connection? Fiber? Wi-Fi? Mobile? Satellite?
Does it drop too nothing or just settle into a constant slower speed? What have you tried to trouble shoot? Is it only rsync or do other tests between the hosts show the same behavior?
Give us more and you might get some help. If these hosts are Linux I would start with iperf to do a more scientific test. And report to us some more info.
selfhosted
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.