ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Maya Licensing and DNS/Certificate Validation The goal is to ensure that Maya can successfully acquire a network license from Autodesk’s licensing server. In many corporate environments the hostname (e.g., license.autodesk.com ) cannot be resolved due to proxy or firewall restrictions, or the SSL certificate presented by the server is not trusted by the clie
Qodana Docker Scanner: Custom CA Trust Store Reload Limitation When running Qodana in a Docker container, users often mount a private CA certificate into the image to allow Maven or NPM repositories to be accessed over HTTPS. The scanner will trust the certificate only after the image’s trust store has been updated and the container restarted. This behavior
I am evaluating NetBox's DNS integration (the netbox-dns plugin) to sync records to an external DNS server that only accepts DNS-over-TLS. The endpoint uses a certificate issued by our internal private CA, and I need to understand how NetBox validates that certificate before committing to this design. My understanding is that outbound validation is handled b
The goal is to determine whether k6, when the `--dns` flag is omitted, applies the search list and resolver options (such as `rotate` and `timeout`) defined in the system’s `/etc/resolv.conf` during hostname lookups initiated by virtual users. DNS results are cached per VU for the test duration and are not refreshed if the underlying record changes, and the
I am writing a Vala application (compiled with valac --pkg gio-2.0 ) that opens a TLS connection using Gio.TlsClientConnection wrapped around a Gio.SocketConnection , with the target host resolved first through Gio.Resolver.lookup_by_name_async . The goal is to have certificate chain validation enforced rather than silently skipped. Two behaviors are unclear
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
Goal Determine whether a running Quarkus application can recognize newly added CA certificates in its truststore without requiring a full restart. Constraints and uncertainty Quarkus relies on the default Java SSLContext unless a custom configuration is provided. The documentation states that truststore changes are not picked up at runtime, but it does not s
Goal: Assess whether developers can override the system DNS resolver used by Laminas\Http\Client\Adapter\Socket when making HTTPS requests. Uncertainty: The adapter currently forwards only host, port, and timeout to PHP’s fsockopen/stream_socket_client, leaving DNS resolution to the underlying OS and offering no built‑in way to inject custom resolvers or DNS
When developing a network client in Zig, a programmer typically resolves a hostname with std.net.DNSLookup and then establishes a TLS connection using std.tls.connect . The DNS resolver returns the IP address but does not automatically supply the resolved host name to the TLS layer for SNI or certificate hostname verification. The application must manually p
maya
docker
qodana
k6
k3os
laminas
zig