Full sync copying dns.interface to other instances - breaks if interface not consistent

[ccruzen]

Use case: 3 different Pi-holes (one Proxmox LXC, one Proxmox VM, one Unraid VM)
Each has a different interface name (ens18, enp1s0, eth0)
If doing full sync, it copies the the primary interface name to the dns.interface field in Pi-hole. Once secondaries FTL is restarted, dns no longer works.
Is there a way to exclude that setting, but still sync the other DNS settings or am I possibly missing somewhere to exclude that?

[ccMatrix]

You can use the FTLCONF_dns_interface environment variable on your container to set the interfaces for each instance explicitly. This is then used instead of what teleporter copies over.

[ccruzen]

You can use the FTLCONF_dns_interface environment variable on your container to set the interfaces for each instance explicitly. This is then used instead of what teleporter copies over.

Thanks for responding, but could you clarify. the FTLCONF_dns_interface variable would be if each Pi-hole instance is a docker container, correct? If so, I don't think this will work in my case as I've installed Pi-hole via the install script, not as docker containers.

[PhilThurston]

No, the FTLCONF_dns_interface is a part of Pihole itself. If you set that ENV variable in your VM or as part of the startup args for your service it will also work. ENV variables that modify settings in Pihole can't be modified or overwritten via the interface or teleporter once the program starts so it would solve this problem. You can always disable full sync and set the env variables of nebula sync to just manually move over the settings you'd like as well.

Edit: Looking at the documentation Pihole suggests for ease of use in non-docker environments that you just edit the pihole.toml file. This will do the same as before preventing teleporter from overwriting the full_sync option: https://docs.pi-hole.net/docker/configuration/

[lovelaze]

Great explanation @PhilThurston! This is indeed the workaround that will solve this issue for now.

In #14 work will be ongoing to implement a more granular way to specify what to include/exclude, that will also be a solution to this