A team switches a Java service's base image to Alpine for size savings and starts seeing intermittent, hard-to-reproduce DNS resolution failures in production only

The same code worked reliably on the previous Debian-based image. Diagnose the likely cause and recommend next steps. Expected reasoning: this is a known category of issue with musl libc's DNS resolution behavior differing from glibc's in certain edge cases (e.g., specific resolver configurations or response handling). Recommend testing DNS resolution behavior explicitly against the Alpine image under the same network conditions as production, checking whether the JDK/runtime in use has a musl-tested variant (rather than a generic JDK manually layered onto generic alpine), and if the issue per