MongoDB's Java driver hasn't really changed anything meaningful from a DNS query and resolution POV for SRV/TXT records, so it's unlikely to be that (not ruling it out entirely).

We should test out a few strategies - for now I'm thinking we could: Expose the connection string as a resource and rely on the model picking it up Add different tools for connecting with atlas ...