[CSHARP-2852] DnsClient.DnsResponseException: Unhandled exception when using mongodb+srv:// Created: 12/Nov/19 Updated: 03/Apr/20 Resolved: 26/Mar/20 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.9.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brecht Vanhaesebrouck | Assignee: | Dmitry Lukyanov (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
docker on ubuntu linux in azure. |
||
| Issue Links: |
|
||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
I cannot connect to mongoDB atlas using an srv record. I am using a peered connection in azure. The host machine itself can resolve the SRV record. I tested it using this command on my ubuntu sever.
An example of my connnection string: mongodb+srv://<username>:<password>@xxxxxxxxx.azure.mongodb.net/test. I am using .net core 3. The base container of my docker container is mcr.microsoft.com/dotnet/core/aspnet:3.0-alpine3.9 . Here's the exception i get:
When using an oldschool connection string (not depending on an srv record) I can connect to my cluster. |
| Comments |
| Comment by Dmitry Lukyanov (Inactive) [ 26/Mar/20 ] |
|
The scope of this ticket will be implemented in |
| Comment by Jeffrey Yemin [ 22/Nov/19 ] |
|
We've talked with the Atlas team and have learned that there have been a few examples of customers on Azure having DNS problems with SRV records. So far we have seen these issues for customers on Azure Windows Webapps and Azure AppServices, but this may impact more Azure services. Can you confirm whether you have an open support inquiry with Azure around this? If not, we suggest you open one up, and please share with us the Azure service context you're using so that we can mention this to our own Azure support contacts. |