Is it possible to disable synchronization of upstream DNS server info?

[farces]

Hello hello, I've recently enabled DNS-over-HTTPS using cloudflared on my two pihole instances, one running on a Raspberry Pi and the other in a docker container on my NAS (primary).

So that I'm not relying on a single cloudflared instance I have that service running directly on the RPi (127.0.0.1#5053), but on the NAS I've had to run it as a separate container named cloudflared (cloudflared#5053). Obvious problem is that I don't want both piholes to use the same upstream DoH server, but I'm also encountering a fatal error during sync because cloudflared doesn't resolve to anything on the RPi and that halts the import during validation.

The only options I think I have (if orbital-sync doesn't have an env. variable to toggle it) is to get cloudflared into the container I'm using so they can both reference 127.0.0.1#5053 which I'd like to avoid just to not have to maintain that, or on the RPi add a hosts entry for 127.0.0.1 cloudflared which somehow tanks the webui periodically.

Completely understandable if pi-hole's teleporter just isn't that granular, though I'd ask because I think this isn't too uncommon of a situation, or at least won't be once more people switch to DoH.

[dreary-ennui]

As of right now, PiHole V6's built in teleporter UI and API functionality only supports all or nothing syncing of the PiHole configuration file (which includes upstream DNS servers), but selective sync support that would allow you to enable/disable syncing of upstream DNS servers is on its way.

Follow PR #567 for updates on this functionality

[farces]

Awesome, thanks for the info. Not sure how I didn't find that PR given you said the exact thing I was looking for in the post itself!

[dreary-ennui]

No worries! I didn't add the upstream DNS server support until this morning after seeing your post :)