Adding a Custom HTTPS Domain to Read the Docs: Minimal Design and Checks
Learn how to serve Read the Docs documentation on your own domain with HTTPS using only a CNAME record and RTFD’s automatic Let’s Encrypt integration.
Loading…
ReadMeFeed / Community knowledge
#dns
Real questions. Useful conversations. Find the people who know your stack.
readthedocsHealth-Aware Service Discovery with Consul DNS
Learn how to use Consul's health-aware DNS to prevent routing traffic to failing service instances, including configuration examples and DNS caching pitfalls.
consulEliminating Hard-Coded IPs with Consul Service Discovery
Stop relying on static IP addresses in your microservices. Learn how Consul uses a service registry and health checks to provide dynamic DNS-based discovery.
Implementing Service Routing with Consul Prepared Queries
Learn how to use Consul Prepared Queries to create stable, named service filters for DNS and HTTP, reducing application complexity and managing failover targets.
How can I diagnose DNS resolution and TLS certificate validation failures in Emacs when retrieving packages from HTTPS archives?
When Emacs attempts to fetch package archives over HTTPS using the built-in url library, it relies on system DNS resolution and GnuTLS for certificate validation. If either step fails, Emacs aborts the operation and reports a generic TLS error, making it hard to pinpoint whether the problem lies in name resolution or in the certificate chain. The goal is to
What TypeScript configuration and typing practices prevent misinterpretation of DNS promise results during TLS certificate hostname validation?
When building TypeScript applications that validate TLS certificates by performing DNS lookups, developers rely on the dns and dnsPromises APIs to obtain A, AAAA, MX, or TXT records. The goal is to guarantee that the type definitions accurately reflect the shape of the resolved data so that certificate hostname validation logic can safely process the results
How can I configure Git to use a custom DNS resolver and a specific CA certificate for HTTPS remotes behind an intercepting proxy?
When cloning or fetching from an HTTPS repository through a corporate proxy that performs SSL interception, Git sometimes fails to verify the server’s certificate because the proxy presents its own CA‑signed certificate. At the same time, the internal DNS used to resolve the repository host differs from the system DNS, causing Git to connect to the wrong add
gitRealm sync times out after DNS migration: Is DNS caching causing the issue?
Problem Context After moving the Realm Object Server to a new IP address, clients report a persistent connection timeout when attempting to open a synced Realm. The SDK continues to use the previous DNS entry, resulting in a failed WebSocket handshake. Constraints & Uncertainty The Realm SDK relies on the platform’s DNS resolver, which may cache entries
What is Azure Public DNS?
Azure Public DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services. You can't use Azure Pub