Use Case

As a Developer
I want the driver to use my injected dns adapter for hostname resolution.
So that I can control service discovery and host lookups in custom environments.

User Experience

• The driver uses the custom resolver and passes the lookup function to the socket layer.

Risks/Unknowns

The most critical risk is ensuring that the lookup method from the DNS adapter is correctly passed into the net.createConnection calls. If missed, the socket might use the system's default resolver instead of the custom one, leading to inconsistent behavior.

Acceptance Criteria

Implementation Requirements

• Remove import: remove require('dns') from all places inside src folder.
• Use dns adapter provided with the mongo client options.

Testing Requirements

• Existing integration tests should pass when custom dns adapter is provided, no node:dns should be imported.

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward