Eliminating 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.
Loading…
ReadMeFeed / Community knowledge
#dns
Real questions. Useful conversations. Find the people who know your stack.
consulImplementing 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
Realtime API: DNS resolution timeout before TLS handshake
Problem Overview When a custom domain is configured for Appwrite’s Realtime service, the client first performs a DNS lookup, then establishes a TLS handshake. A timeout before the handshake indicates a potential DNS or certificate issue. Goal & Constraints The objective is to determine whether the failure originates from DNS propagation (missing A record
Stata internet commands and the OS TLS/DNS stack: distinguishing certificate failures from DNS errors
Stata's internet commands ( copy , urlfetch , webuse , ssc install ) delegate DNS resolution and HTTPS certificate validation to the host operating system and its networking library. Stata does not ship its own resolver or CA store, and there is no documented Stata-level option to disable certificate checks or point to a custom CA bundle. The practical probl
stataScoping certificate-validation bypass in a PowerShell DNS/TLS triage script that must run on 5.1 and 7
Goal I am designing a diagnostic script that separates DNS resolution failures from TLS certificate-validation failures when an internal HTTPS endpoint is unreachable. It uses Resolve-DnsName with -Server and -DnsOnly to compare resolvers, then Test-NetConnection -Port 443 -InformationLevel Detailed, and finally Invoke-RestMethod to surface the TLS error. Co
powershellURLRead certificate validation inconsistency during redirects
The Wolfram Language URLRead function utilizes the underlying operating system's DNS resolver and SSL/TLS stack. Specifically, the VerifyCertificate option governs whether the server's certificate chain is validated against trusted roots. While the default behavior shifted in version 13.3 to maintain backward compatibility, there is ambiguity regarding how t
Web3.js limits on custom DNS resolvers and TLS validation
Goal Establish a secure HTTPS RPC connection from Node.js to a remote Ethereum node while accounting for self-signed or expired certificates and DNS resolution failures. Current behavior Web3.js delegates HTTP requests to the host environment's HTTP client (fetch in browsers, http/https in Node). When the RPC endpoint uses HTTPS, Node's TLS layer validates t
web3js
nodejs
Azure private endpoints: verify DNS before changing the firewall
Understand how Azure private endpoints depend on DNS and routing, then verify the application's hostname resolves to the intended private connection.