How do the DNS servers resolve local hostnames then? The pihole DHCP integration adds local hostnames to DNS when they are assigned an address. If there’s two DHCP servers handing out leases, presumable only one would be accepted, how then would the DNS servers sync those names?
I think I had my secondary pihole resolve local names from the primary, and leases were copied over on a cronjob in case the secondary DHCP server had to be enabled.
Not that it particularly matters for just queries. The problem is that DHCP can only be enabled on one host. If that one fails then devices can’t get on to the network themselves. I’d like to know a good way to have a failover DHCP server - my janky cronjob isn’t great.
Where do you do DHCP? I had a primary pihole with DHCP enabled and a secondary with a cron job that enabled DHCP if the primary was down or disabled it if the primary was working. The cron job did sync DHCP leases from one to the other but it was a bit janky. I tried to update the secondary to pihole v6 and hosed it so I have no backup for now. I’d like to re-image the secondary and get a better setup - when I have time.
Edit to say I really wanted to try keepalived - that’s really cool to fail over without clients noticing.
Ah, I saw another comment about this. The free plan is 300,000 queries a month. That’d last me almost a week before it stops working.
That says it will only function for 300,000 queries per month. Based on my last 24 hours from pi-hole, that wouldn’t even last a week. Are you using a paid plan?
I would encourage you not to split things up too finely. A single repo for your environment would allow you to see all related changes with git. E.g. if you set up a new VM it might need a playbook to set something up, a script to automate a task, and a DNS entry. With a well put together commit message explaining why you’re making those changes there’s not much need for external documentation.
Maybe if you want some more info organised in a wiki, point to the initial commit where you introduced some set up. That way you can see how something was structured. Or if you have a issue tracker you can comment with research on something and then close the issue when you commit a resolution.
Try not to have info spread out too much or maintaining all the pieces will become a chore. Make it simple and easy to keep up.
Usually aluminium or glass. There’s a metallic coating applied to the outside surfaces that stores the data. That layer is very thin though, so most of the material is the substrate.
Oh right, that makes sense. I was only thinking of Matter as serving low bandwidth devices but it also runs over WiFi and ethernet so I guess it can do video for security cameras etc. and evidently Casting audio and video also.
Also Matter is the smart home interop standard. Seems close enough for some confusion in what Matter compatible means on a device.
If you have the
docker-compose.ymllocally, you cannix run github:aksiksi/compose2nixto translate it into a nix file for inclusion in your nixos system config. I think that could be done in the config itself with a git url but I’m not that great at nix. You will surely still need some manual config to e.g. set environment variables for paths and secrets.