CentOS 8's systemd-resolved resolv.conf symlink: mixed resolver behavior and TLS trust mismatches
Goal On CentOS 8, systemd-resolved is active by default and manages /etc/resolv.conf as a symlink to /run/systemd/resolve/stub-resolv.conf , with the stub listener on 127.0.0.53. I need a reliable way to troubleshoot name resolution and TLS certificate validation across tools that may not all consult the same resolver path. Constraints and uncertainty Some u
centos