ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DNSSEC validation failed in Rocky Linux 9 The goal is to enable DNSSEC validation for applications that demand it. In Rocky Linux 9, systemd-resolved disables DNSSEC by default, leading to errors such as DNSSEC validation failed or DNSSEC not enabled . This default setting impacts services that rely on strict DNSSEC enforcement, including some browsers and c
Goal Investigate whether systemd‑resolved should enable DNSSEC validation by default on Arch Linux, given the trade‑off between security and compatibility with public DNS providers. Constraints and Uncertainty The shipped /etc/systemd/resolved.conf sets DNSSEC=no . Enabling DNSSEC can cause resolution failures for domains served by providers that do not publ
Goal Determine whether systemd-resolved DNSSEC validation is enabled on a fresh Rocky Linux 9 installation, and how this setting interacts with TLS certificate validation. Constraints systemd-resolved is installed by default but not enabled; DNSSEC is OFF unless configured. Enabling DNSSEC requires trust anchors; misconfiguration can break name resolution an
The goal is to clarify the documented interaction between IBM Cloud Internet Services DNS resolution and IBM Cloud Certificate Manager SSL/TLS certificate validation when a zone uses DNSSEC and contains ALIAS records that resolve to external domains. CIS supports authoritative DNS with A, AAAA, CNAME, ALIAS and DNSSEC. Certificate Manager validates hostnames
DANE Validation and DNSSEC Dependency OpenSSL provides experimental support for DNS-based Authentication of Named Entities (DANE) via the -dane flag in s_client . This feature allows the client to retrieve TLSA records to verify TLS certificates, reducing reliance on traditional Certificate Authorities. A critical requirement for DANE security is the authent
rockylinux
archlinux
openssl