Get a better job so you can afford better drugs. This is “Minimum Wage Methy”, and you want to be “Salaried Methy”.
The failure rate is going to be absolute INSANE as well.
This ONLY works at an insane scale. This will never hit the consumer market.
Gotta say… This is not how you’d generally do any of this. Where you get this info?
Then something has changed about the local deployment and concentration of the network near you. Don’t know what to tell ya 🤷
As long as the provider is the same, and your instances are using properly using DoH or DoT, you have nothing to worry about.
If you’re super concerned though, I’d be using Mullvad over Cloudflare though. Just saying.
See my other response. This is quite normal.
Yes, that’s called Round-Robin Load Balancing.
To get more specific, your DNS provider spins up a large number of DNS resolvers out in the world on a CDN network that resolves clients to the most geographically convenient server(s) at any point in time based on the GeoIP info of your public IP.
Once you resolve one set of addresses at any given time, it caches your request, so the next time you ask these DNS servers for something you’ll get a response right back from them as fast as possible.
You constantly checking is just going to show this. It’s quite normal.
Your public IP is DHCP. It changes from time to time. Nothing weird about that.
Any of the other IP’s in the DNS Servers list changing is just what you get pointed to when resolved based on your GeoIP location.
I might be misunderstanding, but you’re checking what exactly for DNS leaks?
If the IPs are changing, that’s not uncommon. The HOST changing would be though, like if you swapped from what you expected back to Comcast or something.
You need to get better control of your local network and not have to be paranoid about this. Static reservations for long lived hosts, your router should have a setting to override and prevent internal hosts (like guests) from sending OoB DNS requests, and any sort of VPS stack should as well.
HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.
As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it’s going to miles.kore efficient for this use than a regular PC.
It’s not the CPU. All that will do is consume CPU and raise your energy bill.
In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.
I’ve made a few, but they were quite specific in their purpose. The esp32 ecosystem is pretty great for this purpose, but generally I find people won’t take the time to fuss around with making their own anything when off the shelf varieties are cheap.
You’re describing a CDN. You can’t afford it.
I’d look more into boosting whatever your uplink is versus trying to distribute to localized users.
Well, firstly, it’s not what Tailscale is meant for. I’m getting downvoted by the people using the wrong tool for the wrong job.
You don’t install a VPN on all your local machines just to talk to each other. That’s insane. You especially don’t install one that, while misconfigured, is sending all of its traffic OUTSIDE of your local network, then back in. This is what Tailscale on a number of local machines will do by default.
The way Tailscale works is by installing a Wireguard client on a machine. It then checks in with their DERP servers to figure out it’s network situation (behind NAT, peers in the network, routing tables…etc). So when you have more than one client on the Tailscale network, it automagically assumes some things, the first being that these two machines dont have a more direct route to talk to each other.
So then it will attempt to bridge a path between the DERP server each client is checked into, and pass traffic that way. Which means you then have two machines on the same local network sending traffic OUTSIDE of that network, then back in to complete a VPN network.
This is stupid.
You setup multiple different networks and use exit nodes to bridge two networks together with Tailscale. That’s the entire point. This means setting up routes to let the orchestration layer know that a set of certain machines exist in the same network, and shouldn’t use Tailscale to communicate with each other. Then it will only be using routes for REMOTE networks, where other clients exist, to pass traffic over the Tailscale network.
May I ask what you were planning on doing with Tailscale? I can point you in the right direction.
https://gist.github.com/camullen/0c41d989ac2ad7a89e75eb3be0f8fb16
Just cut Windows out as much as possible and run everything in WSL. Setup everything to boot straight to all your WSL layers, and aside from the absolute shit Base OS, it should be the same.
Yeah, it’s just a simple scheduler. It’s not doing anything fancier than that unless you setup other automations for it to do so. It’s pretty much the same thing you can get from the thermostat itself, so no real reason to run it from HA unless you’re making it pay attention to other sensors or rules.
The thermostat and Ha operate independently, so if you happen to accidentally have some schedule or rule defined on the thermostat itself, it will still execute. Check that first.
Next, you need to check your event and trigger logs for your defined schedule or rules and be certain about the if/when they are/aren’t firing. It should be pretty clear what’s going on there, and if there is a potential time zone issue with this package you’ve installed.
Move your Nginx pets to something else. Pretty simple.
Logs