Can 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
nestjs