ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Fedora utilizes systemd-resolved as the primary DNS manager, operating a stub resolver at 127.0.0.53 . While this manages per-link DNS routing and local caching, a behavioral discrepancy occurs when applications bypass the D-Bus interface to read /etc/resolv.conf directly. The standard configuration relies on /etc/resolv.conf being a symlink to /run/systemd/
When building a NestJS application that relies on the injected HttpService for outbound HTTPS calls, I need to ensure that all requests use a specific DNS resolver (e.g., an internal DNS server) and optionally relax certificate validation for internal services with self‑signed certificates. The HttpService is a thin wrapper around Axios, which ultimately use
Integration boundary between systemd-resolved and NetworkManager DNS stub resolvers The goal is to maintain a stable DNS configuration that prevents intermittent resolution delays which can exhaust application connection pools under load. When both services are active, they may alternately rewrite /etc/resolv.conf between the systemd-resolved stub (127.0.0.5
Azure DNS is a hosted DNS management and name resolution service. You can use it to create public DNS names for other applications and services that you deploy in Azure. Creating a name for an Azure service in your custom domain is simple. You just add a record of the correct type for your service.
Azure Private DNS provides a reliable and secure DNS service for your virtual networks. Azure Private DNS manages and resolves domain names in the virtual network without the need to configure a custom DNS solution. By using private DNS zones, you can use your own custom domain name instead of the A
Goal Investigate how DNS resolution and TLS certificate validation behave when Capacitor HTTP requests are routed through the embedded Web View versus a native HTTP client, and determine the impact on app reliability when system DNS or certificate stores change. Constraints & Uncertainty Capacitor’s default HTTP plugin uses the Web View’s networking stac
When migrating a small application to new infrastructure using Consul for service discovery, the goal is to achieve zero downtime by leveraging health checks to steer traffic. In this architecture, the Consul DNS interface is used to resolve healthy service instances. A potential conflict arises when a service instance is marked as critical . While the Consu
Laravel HTTP Client and System DNS Resolver The goal is to understand why SSL certificate validation sometimes fails when the Laravel HTTP Client resolves a host that has been cached by the underlying PHP‑FPM DNS resolver. The Laravel HTTP Client relies on Guzzle and ultimately cURL, which in turn uses the OS resolver and the CA bundle specified by curl.cain
In a k3os environment, CoreDNS operates as a system-wide addon managed by the kube-controller. When deploying on edge nodes with specific upstream DNS providers, resolution often fails because the node's resolv.conf conflicts with the CoreDNS configuration in the k3s manifest. Furthermore, because k3os utilizes a read-only root filesystem by default, injecti
fedora
nestjs
archlinux
capacitor
consul