In the investigation of HELP-38552, it turned out that the driver did not parse the SRV hostname correctly for any URI with a username and password. e.g, for a URI of mongodb+srv://<USER:PASS>@<HOST>/<PATH>, the hosts was set to <USER:PASS> instead of <HOST>. Therefore, the driver could not connect to the SRV server to get topology updates after the initial SRV call. The connecting error was not returned or logged, either.