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.
SSL certificate validation failure during systemd-resolved DNS stub integration
On Arch Linux, integrating systemd-resolved typically involves linking /etc/resolv.conf to /run/systemd/resolve/stub-resolv.conf to utilize the local DNS stub listener at 127.0.0.53. When this configuration is active, certain applications may encounter SSL/TLS handshake failures if the DNS resolution process introduces latency or returns unexpected records t
archlinux
Delegate an Azure DNS subdomain
You can use the Azure portal to delegate a DNS subdomain. For example, if you own the adatum.com domain, you can delegate a subdomain called engineering.adatum.com to another separate zone that you can administer separately from the adatum.com zone. You can also delegate a subdomain using Azure Powe
Which approach preserves cloud-init DNS settings across reboots in k3os?
The goal is to keep custom DNS servers supplied via cloud-init after a k3os node reboots. During early boot, cloud-init writes the nameservers to /etc/resolv.conf, but k3os later runs a DNS reconciliation loop that regenerates /etc/resolv.conf from static files in /etc/rancher/k3os/dns, overwriting the cloud-init values unless those files are also updated. I
k3osCan NestJS HttpService be configured with a global custom DNS resolver?
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
nestjsHow Azure DNS works with other Azure services
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.
What is Azure Private DNS?
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
Capacitor Web View Networking vs Native HTTP Client: DNS & TLS Interoperability
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
capacitorCritical health state propagation delay in Consul DNS
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
consul