3 ms·
I disagree. The nameservers still respond to requests on 53/tcp. It seems like someone messed up a firewall configuration or rolled out a bad server configurati
by raphman 2y ago
I disagree. The nameservers still respond to requests on 53/tcp. It seems like someone messed up a firewall configuration or rolled out a bad server configuration. Shit happens - maybe exacerbated by the DOGE insanity. But there is no indication that this was done on purpose.
- kube-system 2y agoThe insanity that has/will lead to functions no longer being properly staffed is on purpose.