Skip to content

Explain how to revert to default DNS client in the mongodb extension to resolve mongo+srv:// urls #46812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 17, 2025
+18 −3
Merged

Explain how to revert to default DNS client in the mongodb extension to resolve mongo+srv:// urls #46812

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 18 additions & 3 deletions docs/src/main/asciidoc/mongodb.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,10 +235,24 @@ In this example, we are using a single instance running on localhost:
quarkus.mongodb.connection-string = mongodb://localhost:27017
----

If you need more configuration properties, there is a full list at the end of this guide.
=== Resolving mongo+srv:// URLs

WARNING: By default, Quarkus will restrict the use of JNDI within an application, as a precaution to try and mitigate any future vulnerabilities similar to Log4Shell.
Because the `mongo+srv` protocol often used to connect to MongoDB requires JNDI, this protection is automatically disabled when using the MongoDB client extension.
When using `mongo+srv://` URLs, the MongoDB driver resolves DNS SRV records to retrieve the list of hosts to connect to.
By default, it relies on a DNS client implemented using JNDI.

For security reasons, Quarkus restricts JNDI usage within applications to help mitigate potential vulnerabilities like Log4Shell.
To support `mongo+srv://`, Quarkus provides an alternative DNS client.

However, in some environments, this alternative DNS client may be unable to resolve `SRV` records.
If you encounter such issues, you can revert to the MongoDB driver’s default DNS client by setting the following properties:

[source, properties]
----
quarkus.naming.enable-jndi=true
quarkus.class-loading.removed-resources."io.quarkus\:quarkus-mongodb-client"=META-INF/services/com.mongodb.spi.dns.DnsClientProvider
----

This restores the default JNDI-based resolution mechanism used by the MongoDB driver.

[[dev-services]]
=== Use the MongoDB Dev Services
Expand Down Expand Up @@ -777,6 +791,7 @@ public class MyCustomizer implements MongoClientCustomizer {

IMPORTANT: Client-side field level encryption, and feature relying on https://github.com/mongodb/libmongocrypt[Mongo Crypt] in general, are not supported in native mode.


== Configuration Reference

include::{generated-dir}/config/quarkus-mongodb-client.adoc[opts=optional, leveloffset=+1]
Loading