ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Search Domain Appending Behavior In Linux environments using the glibc resolver, the ndots configuration in /etc/resolv.conf defines the minimum number of dots a name must contain to be considered an absolute domain name. When a query name contains fewer dots than the ndots threshold, the resolver attempts to append the configured search domains before attem
Jasmine fake timers and Node.js DNS lookup callback timing The goal is to write a unit test that exercises DNS‑resolution logic while using Jasmine’s fake‑timer utility to make all asynchronous callbacks fire synchronously, enabling deterministic, fast test execution. However, Jasmine’s jasmine.clock() only replaces JavaScript‑based timers (setTimeout, setIn
Background The Opera Browser includes a built‑in VPN that routes traffic through a dedicated server network. Official documentation states that the VPN should handle all traffic, but it does not explicitly indicate whether DNS queries are forced through the VPN or may be resolved by the host operating system. Unresolved Decision When the "Use system DNS" opt
Cross-Domain Query Access with TLS in Jaeger Jaeger UI makes API calls to /api/traces using same-origin policy by default. When the UI is served from a different DNS name than the collector endpoint, the browser enforces CORS restrictions that can block query requests. Two documented approaches exist for resolving this constraint with TLS-secured collector a
The goal is to determine whether a Kubeflow pipeline pod can validate TLS certificates of external HTTPS endpoints without manually adding the cluster’s root CA bundle to the container image. Current behavior varies with the pod’s base OS, the presence of the SSL_CERT_FILE environment variable, and whether the kube-root-ca.crt volume mount is automatically a
I'm deploying a static JAMstack site behind a CDN and need to decide how to handle the root domain ( example.com ) alongside www.example.com . The CDN provides edge hostnames, and I understand a CNAME works fine for the subdomain but is not valid at the zone apex, so the apex typically needs an ALIAS/ANAME record or a flattened CNAME, depending on the DNS pr
Goal: Ensure that an ESXi host can be successfully enrolled to a vCenter Server without SSL certificate validation errors related to DNS resolution. Constraint: The validation performed by the vSphere Certificate Authority (VMCA) requires that the forward and reverse DNS lookups for the host's FQDN are consistent and that the PTR record matches the FQDN cont
Symptom When the IP address associated with a hostname used by an Ecto.Repo changes after the connection pool has been started, existing connections continue to resolve to the former address until the pool is recycled. The underlying behavior stems from Erlang’s :inet resolver being called only when a socket is first opened, and SSL/TLS certificate validatio
The DNS protocol prevents the assignment of a CNAME record at the zone apex. An example zone apex is contoso.com. This restriction presents a problem for application owners who have load-balanced applications behind Traffic Manager, because a Traffic Manager profile is normally referenced with a CNA
nodejs
opera
jaegertracing
kubeflow
jamstack
ecto