ATC_MiThermometer VS CoreDNS

I want to do a little IOT project where I establish a MQQT-Broker on my Raspberry Pi and send it readings from my measurement devices (xiaomi Mijia-LYWSD03MMC). The plan is for these devices to connect to my ESP32, allowing me to transfer data to the broker on the Pi. I've successfully connected my ESP32 to my Wi-Fi and to my broker, but I'm experiencing significant difficulties in connecting it to my two measurement devices. I have essentially followed the instructions provided in this GitHub repository (https://github.com/atc1441/ATC_MiThermometer) as best as I could. I also checked some other repos but they didn't really help me as they were too big/complex...

If you get off WiFi and on Bluetooth: https://github.com/atc1441/ATC_MiThermometer They last a year with a single CR2032 which is hard to do with WiFi.

I then copied this Python script to the Raspberry Pi 4 and was able to read the temperature and humidity! (https://github.com/atc1441/ATC_MiThermometer/tree/master/contrib/python)

I’m using 16pcs Xiaomi Thermometer LYWSD03MMC BLE thermometer around the house with custom ROM from here https://github.com/atc1441/ATC_MiThermometer

I use the Xiaomi (pronounced Show Me) Mi Temperature and Humidity monitors (version 2) and flash the firmware with a 'open source' version (here or the older one here). I've found battery life good (8 months + with the newer software on one sensor) and bar from one corrupt display (right next to an outdoor electricity feed - well the box is handy and dry) then they have just run and run and run.

The thermometers in screenshot are Xiaomi Thermometer LYWSD03MMC with ATC custom firmware. Their bluetooth broadcast data collected by some cheap chinese ESP32 board and ESPHome addon in Home Assistant.

You can replace their firmware with one which is more open and broadcasts the values without needing to connect to the device: https://github.com/atc1441/ATC_MiThermometer

CoreDNS supports this via the bind plugin.

I'd like to use Cloudflare's 1.1.1.1 and 1.0.0.1 nameservers in Kubernetes, alongside DNS over TLS. It looks like I can do it using core-dns. I need to setup the following somehow:

Shamless plug for CoreDNS. Much better DNS server than classic bind9. And of course there's already a nice container image for it.

But another approach that could work in Kubernetes, because the DNS servers are within the cluster itself, would be to work directly with the DNS server pods. In most Kubernetes clusters, whether standalone or managed (GKE, AKS, EKS), the cluster DNS is either coredns or kube-dns. That was great to minimize how much configuration options we’d need to support. We realized we could edit the coredns or kube-dns configmap resources to enable their log option, which would make them log all the queries they handle. We’ll cover exactly how it’s done in more detail below.

CoreDNS has an ectd plugin, so your service could add entries to a database, which is used as record source. Not the same mechanism as you have described, but it will get the job done. Also this is what Kubetnetes does for incluster dns records.

nevermind there's caddy builtin upgrade method https://github.com/coredns/coredns/issues/6034

Coredns can be spun up in a docker container, just starting to get into it myself

CoreDNS is a pretty good DNS server.

Core DNS (https://coredns.io).