Does nebula-sync sync custom dnsmasq configurations

[bandlaw12]

Since Pi-hole doesn't have a wildcard sync, I have setup a custome dnsmasq.d config in my /etc/dnsmasq.d/ for my wildcard domain and while the updated configuration synced, the custom config file did not sync. Does nebula ignore those or is there a configuration issue on my end? Thank you in advance for any help - I had a bear of a time with rsync so I'm very grateful for this project!

Platform: Synology container manager (docker), 20.10.23-1437 (I haven't done the upgrade to 24.0.2 yet)

nebula-sync version: 0.10.0
config: Set to "FullSync=true"

logs:
2025-04-18T14:50:00-04:00 INF Running sync mode=full replicas=2

2025-04-18T14:50:00-04:00 INF Authenticating clients...

2025-04-18T14:50:00-04:00 INF Syncing teleporters...

2025-04-18T14:50:00-04:00 INF Syncing configs...

2025-04-18T14:50:00-04:00 INF Invalidating sessions...

2025-04-18T14:50:00-04:00 INF Sync completed

[lovelaze]

Hi @bandlaw12

Custom dnsmasq config files under /etc/dnsmasq.d/ will not be synced, I also don't think the pihole API supports this.

I'm not sure what custom configuration you have, but perhaps you can make use of the pihole setting misc.dnsmasq_lines instead. It supports injecting separate lines into the generated dnsmasq configuration /etc/pihole/dnsmasq.conf

That setting can be synced

[bandlaw12]

This worked great, thank you! Is it possible to add this to the readme? If that's something contributors can do I'd be glad to take a stab at it if you want - or here's something I hope you could copy & paste (probably at the bottom just above the Disclaimer section unless you prefer it elsewhere.) Thank you again!

Wildcard or dnsmasq.d configuration

Custom dnsmasq config files under /etc/dnsmasq.d/ will not be synced, as the pihole teleport API does not currently support this. Instead, you you can make use of the pihole setting misc.dnsmasq_lines instead. It supports injecting separate lines into the generated dnsmasq configuration /etc/pihole/dnsmasq.conf. It does support comments, and here's a sample entry (note the lack of a * on the domain name):

address=/yourdomain.net/192.168.0.0 # wildcard for subdomains to redirect to reverse proxy.

You'll want to change both the domain, the IP address and the comment to suit your needs, of course! This will properly sync (tested as of version 0.10.0) using nebula-sync.