Why can a DNS change work on one device but not another?
Why can a DNS change work on one device but not another? This Q&A focuses on interpreting the evidence before changing application or network settings.
Loading…
ReadMeFeed / Community knowledge
#dns
Real questions. Useful conversations. Find the people who know your stack.
IntelliJ plugin repository unreachable behind proxy: DNS failure or TLS certificate validation error
IntelliJ plugin repository unreachable behind proxy: DNS failure or TLS certificate validation error The goal is to determine why IntelliJ IDEA cannot reach the plugin repository when operating behind a corporate proxy. The Plugins dialog returns a generic connection failure, and the proxy connection test only confirms basic reachability, not a successful TL
intellijTLS hostname verification error when connecting to InfluxDB via DNS name
Problem InfluxDB OSS 2.x serves HTTPS using a certificate whose Subject Alternative Name (SAN) may not include the DNS name used by the client. When the client resolves the host via DNS and initiates a TLS handshake, the hostname verification fails and the connection aborts before any data is exchanged. This manifests as a generic “connection error” or timeo
Custom Domain HTTPS on Read the Docs: Unresolved Wildcard Certificate Support
Goal To understand the current limitations and future plans for serving multiple subdomains under a single custom domain on Read the Docs using HTTPS. Constraints Read the Docs automatically issues a free Let's Encrypt certificate for each custom domain that points to readthedocs.org via a CNAME (or an A/ALIAS record for apex domains). The platform does not
readthedocsLimits: Custom DNS resolver vs Host header mismatch in Ktor client
Goal We want to issue an HTTPS request to a server identified by an IP address while setting the Host header to a domain that has a valid TLS certificate. The request should perform DNS resolution via a custom resolver so that the domain maps to the desired IP, and the TLS handshake should validate the certificate against that domain. Constraints Using the d
ktorFaunaDB custom domain: DNS resolution error before TLS handshake
Symptom A client cannot establish a TLS connection to a FaunaDB instance accessed via a custom domain. The connection attempt terminates with a DNS resolution error (“Name or service not known”) before any TLS handshake occurs. Goal Determine whether the failure stems from an incorrect or missing DNS A record, an overly restrictive CAA record, or a certifica
Per‑project DNS and SSL configuration missing in GoLand HTTP client
GoLand’s integrated HTTP client inherits the operating system DNS resolver, preventing per‑project DNS configuration overrides. The SSL/TLS verification layer relies on the JVM default truststore, which cannot be customized for individual modules, leading to validation failures with self‑signed or corporate certificates. These limitations cause inconsistent
golandAppwrite Self-Hosted SDK Endpoint and Reverse-Proxy TLS: Which Hostname Must Match?
In a self-hosted Appwrite deployment, TLS is normally terminated by an external reverse proxy while the Appwrite containers serve plain HTTP on the internal network. SDK clients connect to the endpoint URL configured for the project and validate the presented certificate against that URL's hostname using the underlying HTTP client's default trust store. The
Does Sema Validate Certificate Chains or Only CT Log Inclusion?
Clarifying Sema’s Validation Scope Sema ingests Certificate Transparency (CT) logs and indexes DNS names from certificates for domain queries. The tool verifies log signatures and Merkle consistency, but it is unclear whether it performs full X.509 path validation against a trust store. Unresolved Design Decision The repository documentation notes that Sema
sema