[GODRIVER-896] Document Docker DNS issue Created: 22/Mar/19  Updated: 28/Oct/23  Resolved: 09/Apr/19

Status: Closed
Project: Go Driver
Component/s: Documentation
Affects Version/s: None
Fix Version/s: 1.0.1

Type: Improvement Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Kristofer Brandow (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by GODRIVER-950 Backport "Document Docker DNS issue" Closed

 Description   

See GODRIVER-829. While we don't currently consider this a driver bug, it has been affecting users and we should document it somewhere so that it's easier for people to resolve (no pun intended) the issue themselves.



 Comments   
Comment by Githook User [ 09/Apr/19 ]

Author:

{'name': 'Kris Brandow', 'username': 'skriptble', 'email': 'kris@mongodb.com'}

Message: Document DNS issues with Go 1.11+ and mongodb+srv

GODRIVER-896

Change-Id: I69ac5758f1300cecbe8b20714afa93eaa84420a3
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/4997eb4097c63e341943a19f8d9eb33e27642459

Comment by Kristofer Brandow (Inactive) [ 09/Apr/19 ]

Code Review: https://review.gerrithub.io/c/mongodb/mongo-go-driver/+/450654.

Comment by Jeffrey Yemin [ 09/Apr/19 ]

Specifically, we should document that `mongodb+srv` connections strings are incompatible with Go 1.11+ when used with some DNS servers that are used in the wild, due to the change introduced in https://github.com/golang/go/issues/10622. We can suggest that if they get the error cannot unmarshal DNS message that they try using a different DNS server.

Generated at Thu Feb 08 08:35:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.