NetBeans Proxy Settings and SOCKS DNS Resolution

Apache NetBeans manages connectivity for plugin updates and Maven dependency resolution through the internal Proxy Settings menu. When working within corporate environments that bypass system DNS in favor of a SOCKS proxy, the IDE must correctly route hostname resolution to the proxy server to avoid connectivity failures.

There is a distinction between the proxy settings configured in the UI and the JVM arguments defined in netbeans.conf. When a SOCKS proxy is enabled, it is unclear how the IDE handles the transition between the launch JDK's default network behavior and the specific proxy constraints required for internal repository DNS resolution.

• Does the "SOCKS" proxy configuration in the Options menu automatically trigger the socksProxyHost and socksProxyPort JVM properties?
• Is a separate -Dsun.net.spi.nameservice.nameservers argument required in netbeans.conf to ensure DNS resolution occurs on the proxy side rather than the local host?