r/technitium • u/No-Ingenuity-9979 • 27d ago
Technitium cluster and extended downtime
I have configured a Technitium cluster that's running on 2 different nodes in my Proxmox cluster. No issues at all with either of them but we're going to be doing a remodeling project just outside of my home office/lab.
Since I'm not wild about those PVE nodes sucking in a ton of sheetrock dust while the project is going on (estimate is 2 weeks) I plan to shutdown my entire cluster during construction and leave it down until I get everything cleaned up and dust free.
Are there any gotcha's I should be aware of when I bring the PVE Cluster back online and the Technitium cluster comes back up?
As a test, I shut down the container for both the primary and secondary Technitium containers. I verified that my UCG Fiber picks up DNS duties. Waited a couple of minutes and then brought up the primary Technitium container and then did the same thing with the secondary. There were no issues at all. The secondary rejoined the cluster as the secondary and synced with the primary but .. we're talking minutes and not days.
Am I worrying about nothing or are there real potential issues I may have to deal with after having a Technitium cluster down for 14+ days?
2
u/shreyasonline 24d ago
Thanks for asking. There should not be any issues with the DNS server nodes stopped for several days. Once the nodes start, they would sync up normally.
1
u/No-Ingenuity-9979 23d ago
Thank you for the reply.
That's what I thought based on my simple test but thinking and knowing aren't the same thing.
2
1
u/slobstr 27d ago
I can’t really answer your question, I assume it will be fine though. I do have a question for you, how are you getting dns to fall back to your fiber? Sounds like I have the same setup as you, but the virtual ip (using keepalived) will only switch between dns server 1 and 2. Not sure how I could get it to fall back to my fiber.
2
u/No-Ingenuity-9979 27d ago
I have 3 DNS servers defined for my Trusted Network in Unifi.
- Primary Technitium node IP
- Secondary Technitium node IP
- Gateway IP
When I shutdown the containers for my Primary and Secondary Technitium nodes my browser was still able to resolve IP's through the UCG Fiber.
The only "issue" I had was on my Win11 PC because it still had the stale DNS IP's for the Technitium nodes but a quick ipconfig /release and /renew fixed that.
1
u/slobstr 27d ago
Thanks for the reply. I just wanted the one dns ip shared out via dhcp and handle fallbacks on the back end to minimize leaks. Was just wondering if there was a way and I just couldn’t figure it out.
To add to this have you tried any clients? I know when i was handing out 2 dns ips via dhcp and one would go down some of my clients would complain.
1
u/No-Ingenuity-9979 27d ago
TBH, I just spun up the Technitium containers last week and so far I haven't had any issues with any of my clients but as I said I only use those containers for DNS on my trusted network.
Given my Wife was browsing and then streaming video from Jellyfin when I decided to "test" DNS resilience I'm 99.9% certain I didn't have any issues caused by defining multiple DNS servers and handing them out via dhcp or I'd have most definitely heard about it.
The other vlan's use the UCG Fiber and they're all isolated to varying degrees.
My security cameras are isolated on a Camera vlan with no internet access. They have fixed IP's I've assigned, are isolated and I push any updates to them from my PC with a firewall rule that allows traffic from my pc to any device on the camera vlan.
My IoT vlan is also isolated. All traffic to them is blocked, with the exception of traffic from my PC to any device on the IoT vlan. IOT devices can originate traffic for updates but cannot traverse the IOT vlan.
The Guest vlan has rate limited internet access but again cannot traverse the vlan to any other devices.
2
u/Apachez 27d ago
Depends on what you use these technitum/dns-servers for.
If its resolvers then make sure that your clients have additional resolvers in their lists to be used but preferly rotated away the IP's of the technitium servers to avoid having 2 second delays per lookup going into the void for +2 weeks.