Yeah, I'm looking to replicate my local DNS records...Settings | Local DNS Records is what I'm after, I don't want to change the resolver information since that's unique to each instance. I set the SYNC_CONFIG_DNS=true but that actually generated the following error: ERR Sync failed error="sync configs failed: unexpected status code: 400". Changing it back to false does not generate the error. Any thoughts?
Thanks!
Hmm, it should only post to the replicas what is returned from the primary. Are they both running newer v6 versions? It sounds like funky config.
If you can PM me your dns config output I can have a look. replace host and password:
curl -X GET "https://pihole/api/config/dns?detailed=false" -H "sid: $(curl -X POST 'https://pihole/api/auth' -d '{"password": "X"}' | jq -r '.session.sid')" | jq
The long term goal for nebula-sync is to have an ever more granular way of deciding what to sync. Perhaps a web interface.
Just wondering if Pi-hole and Orbital-Sync teams would consider merging into Pi-hole.
Hi! I just finished writing my own lightweight Python sync script yesterday and then discovered Nebula Sync. You've done a great job filling the gap Gravity Sync left for v6 users.
I wanted to point out a potential risk regarding the blacklist approach used in SYNC_CONFIG_DNS_EXCLUDE.
If a future Pi-hole update (e.g., v7) adds a new hardware-specific setting under the [dns] section, Nebula will automatically sync it because it's not yet on the exclude list. If that setting depends on specific hardware (like a specific interface or IP binding), it could break the secondary instance.
Have you considered using a whitelist approach for the config sync instead? Syncing only known-safe keys (like hosts and cnameRecords) would make it safer against future upstream changes.
Hi @Veyo!
Did you try out the include filters instead of exclude? As in SYNC_CONFIG_DNS_INCLUDE
It is the whitelist equivalent and probably what you’re after 