[SERVER-34563] Connect via SRV record fails if the returned record resides in subdomain Created: 19/Apr/18 Updated: 29/Oct/23 Resolved: 26/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.6.3 |
| Fix Version/s: | 3.6.6, 4.0.1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexey Eremenko | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian GNU/Linux buster/sid |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||
| Sprint: | Platforms 2018-06-18, Platforms 2018-07-02 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 67 | ||||||||||||
| Description |
|
Kubernetes supports DNS SRV (service) records for named ports As we can see the host resides in the service subdomain and the software throws an error. |
| Comments |
| Comment by Githook User [ 28/Jun/18 ] |
|
Author: {'username': 'adamlsd', 'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com'}Message: The current implementation of DNS name processing uses raw string (cherry picked from commit 181c43bd006666b07441bb3be61b7324ef7dcc80) |
| Comment by Githook User [ 26/Jun/18 ] |
|
Author: {'username': 'adamlsd', 'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com'}Message: The current implementation of DNS name processing uses raw string (cherry picked from commit 181c43bd006666b07441bb3be61b7324ef7dcc80) |
| Comment by Githook User [ 26/Jun/18 ] |
|
Author: {'username': 'adamlsd', 'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com'}Message: The current implementation of DNS name processing uses raw string |
| Comment by David Golden [ 26/Apr/18 ] |
|
There is a driver spec test case to address a related case: https://github.com/mongodb/specifications/blob/master/source/initial-dns-seedlist-discovery/tests/longer-parent-in-return.json Given mongodb+srv name test18.test.build.10gen.cc, an SRV resource record referencing localhost.sub.test.build.10gen.cc is allowed. If localhost.sub.test.build.10gen.cc is allowed because it shares the parent "test.build.10gen.cc", then it should also be allowed for there to be hostA.test18.test.build.10gen.cc, which is equivalent to the k8s case described. |