[DRIVERS-2083] Codify rules around Driver connection DNS Created: 21/Feb/19 Updated: 09/Jan/24 Resolved: 09/Jan/24 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | CMAP, SDAM |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Daniel Aprahamian (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintainers-close | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
|
@xdg brought up that it would be a good idea to specify a few points about Driver DNS in CMAP. Specifically: 1. Drivers MUST NOT cache DNS results, and always MUST perform a DNS lookup when creating a new connection This might be related to the work in |
| Comments |
| Comment by Valentin Kavalenka [ 09/Jan/24 ] |
|
bailey.pearson@mongodb.com and I decided to close this old ticket after re-triaging it. |
| Comment by Valentin Kavalenka [ 12/Oct/23 ] |
|
The discussion copied from the duplicate DRIVERS-1113. Divjot Arora (Inactive)
Shane Harvey
Divjot Arora (Inactive)
|
| Comment by Jeffrey Yemin [ 25/Feb/19 ] |
|
david.golden sure, that's totally fine with me. |
| Comment by David Golden [ 25/Feb/19 ] |
|
jeff.yemin, the intent is for drivers to only ever rely on their environment's DNS resolver's caching (and TTL management/configuration) and not – for example – store the resolved IP address in the driver and never do a DNS lookup call again. If we clarify that point, are you OK with it being "MUST"? |
| Comment by Jeffrey Yemin [ 25/Feb/19 ] |
|
The JVM, and likely other runtime environments, provide only global, application-level control over DNS caching. See networkaddress.cache.ttl documentation at https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html. I suggest making this a SHOULD at most. |
| Comment by David Golden [ 22/Feb/19 ] |
|
Might go in both places. In particular, CMAP covers creating connections, so DNS lookup seemed more natural there. But it's true for SDAM connections, too, which don't use a connection pool. |
| Comment by Ian Whalen (Inactive) [ 22/Feb/19 ] |
|
note that the clarification here should prob be in SDAM not CMAP. |