ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Diagnose SSL handshake failures that arise when Cassandra nodes connect using IP addresses while the peer’s TLS certificate lists only DNS names. Constraints The cluster runs with require_endpoint_verification=true to enforce hostname checks, but nodes are configured with listen_address or broadcast_address as static IPs. This mismatch triggers javax.ne
Limits of TLS certificate validation in Consul DNS proxy for upstream DNS‑over‑TLS The Consul DNS proxy can forward queries to external DNS resolvers using DNS‑over‑TLS (DoT). Documentation states that the proxy does not perform TLS certificate validation on the upstream server; the client must handle verification. This leaves an unresolved decision about wh
You can use Azure DNS to host your DNS domain and manage your DNS records. By hosting your domains in Azure, you can manage your DNS records using the same credentials, APIs, tools, and billing as your other Azure services. Suppose you buy the domain contoso.com from a domain name registrar and then
As the title says, I need to setup SSL for an app hosted in Azure Container Instances, however, I'm not quite sure where I need to start. I have a containerized app hosted via Azure Container Instances at the address http://myApp.northamerica.azurecontainer.io . This address is masked by the 'official' address at http://api.myApp.com . Is there any reason wh
This article provides an overview of how reverse DNS works, and scenarios in which reverse DNS is supported in Azure. What is reverse DNS? Conventional DNS records map a DNS name to an IP address. For example, assume that www.contoso.com resolves to 203.0.113.100. Reverse DNS does the opposite by tr
PyScript currently relies on the browser's fetch API for all module imports, which means DNS resolution and TLS certificate validation are handled entirely by the underlying OS and browser stack. No attribute or environment variable exists to relax these checks, so developers encountering self-signed or expired certificates must resort to server-side fixes o
Where the fault could sit When an ngrok endpoint on a reserved custom domain shows a hostname-resolution or certificate-validation symptom, the cause could sit in the public DNS record and its CAA rules, in ngrok's asynchronous certificate provisioning, or in the local service behind the agent. The goal is to identify which layer to investigate first before
Azure DNS Private Resolver is a fully managed, highly available service that enables secure and seamless DNS resolution between Azure virtual networks and on-premises environments—without the need to deploy, manage, or patch custom DNS servers. By using this service, you can resolve DNS queries for
In Hadoop clusters utilizing Kerberos security, the framework typically canonicalizes hostnames to build service principals (e.g., nn/host.example.com@REALM ). This process relies heavily on the consistency between forward (A) and reverse (PTR) DNS records to ensure the resolved canonical hostname matches the identity stored in the service keytab. In environ
cassandra
consul
docker
ngrok
hadoop