While creating NNCP in disconnected (air gapped) clusters, where root-servers.net isn't resolvable, there is an extra 2 minutes of delay before NNCP is successfully applied due to DNS probes checking root-servers.net resolve.

It happened two times to me in the last month while performing OCP PoC in air gapped environments.

I'd like to either have it explicitly documented somewhere (requirements for air gapped OCP installations maybe?) or ability to disable that DNS probe.

Please note that expecting root-servers.net is being resolvable in air gapped installations may be challenging as it may require interference with core network infrastructure of highly restricted environments.