Using Firefox DNS‑over‑HTTPS: Setup, Testing, and When to Turn It Off
Learn how to enable, test, and troubleshoot Firefox DNS‑over‑HTTPS, plus when to disable it for split‑horizon networks.
Loading…
ReadMeFeed / Community knowledge
#network-config
Real questions. Useful conversations. Find the people who know your stack.
firefoxHow can I prevent accidental public exposure of gRPC services when using insecure credentials?
I am setting up a gRPC service for internal microservice communication and want to guarantee that the service is never reachable from the public internet, even if configuration files are edited incorrectly. I plan to use TLS with mutual authentication, but I am concerned that an accidental insecure port or missing credentials could expose the service uninten
grpcWhich approach preserves cloud-init DNS settings across reboots in k3os?
The goal is to keep custom DNS servers supplied via cloud-init after a k3os node reboots. During early boot, cloud-init writes the nameservers to /etc/resolv.conf, but k3os later runs a DNS reconciliation loop that regenerates /etc/resolv.conf from static files in /etc/rancher/k3os/dns, overwriting the cloud-init values unless those files are also updated. I
k3osAdmin API remains externally accessible after configuring adminHost for localhost
When securing a Node-RED instance, administrators often set the adminHost property to 127.0.0.1 to limit the HTTP admin API to the loopback interface. The goal is to confirm that this setting alone prevents any external host from reaching the editor UI and deploying flows, while preserving normal flow execution through HTTP input/output nodes. Uncertainty re
nodered