<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:39:08 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[GODRIVER-2679] Improve docs/message for &quot;cannot unmarshal DNS message&quot; error</title>
                <link>https://jira.mongodb.org/browse/GODRIVER-2679</link>
                <project id="14289" key="GODRIVER">Go Driver</project>
                    <description>&lt;h4&gt;&lt;a name=&quot;Summary&quot;&gt;&lt;/a&gt;Summary &lt;/h4&gt;
&lt;p&gt;See &lt;a href=&quot;https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo#hdr-Potential_DNS_Issues&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo#hdr-Potential_DNS_Issues&lt;/a&gt;&lt;br/&gt;
This issue has recently become more severe, due to the following:&lt;br/&gt;
1. Serverless instances require an SRV connection string; there is no workaround as suggested on the internet to switch to a non-srv connection string like for Atlas Dedicated instances.&lt;br/&gt;
2. The server tools (mongodump and mongorestore in particular) are written using the go driver, but the DNS unmarshalling problem is only documented in the Go driver manual.  Users should not have to know how the tools work under the hood to diagnose problems with them.&lt;br/&gt;
3. Particularly vexing is the fact that only the Go driver is affected by this issue, and other drivers are not.  Typically users try to load some existing data into Serverless when they try it out for the first time, so this first-touch experience is particularly sour when they get this error from the restore tool.&lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;Pleaseprovidetheversionofthedriver.Ifapplicable%2CpleaseprovidetheMongoDBserverversionandtopology%28standalone%2Creplicaset%2Corshardedcluster%29.&quot;&gt;&lt;/a&gt;Please provide the version of the driver. If applicable, please provide the MongoDB server version and topology (standalone, replica set, or sharded cluster).&lt;/h4&gt;
&lt;p&gt;The latest version of mongorestore is affected by this issue.&lt;/p&gt;

&lt;h4&gt;&lt;a name=&quot;HowtoReproduce&quot;&gt;&lt;/a&gt;How to Reproduce&lt;/h4&gt;
&lt;p&gt;I&apos;m actually not sure even by looking at &lt;a href=&quot;https://github.com/golang/go/issues/10622&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/golang/go/issues/10622&lt;/a&gt; which specific DNS configurations cause this problem.&lt;/p&gt;


&lt;h4&gt;&lt;a name=&quot;AdditionalBackground&quot;&gt;&lt;/a&gt;Additional Background&lt;/h4&gt;
&lt;p&gt;Relevant slack conversation (will expire soon): &lt;a href=&quot;https://mongodb.slack.com/archives/C02GR4CL0AG/p1670479230213549&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodb.slack.com/archives/C02GR4CL0AG/p1670479230213549&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Documentation:&lt;br/&gt;
&lt;a href=&quot;https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo#hdr-Potential_DNS_Issues&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo#hdr-Potential_DNS_Issues&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="2207116">GODRIVER-2679</key>
            <summary>Improve docs/message for &quot;cannot unmarshal DNS message&quot; error</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="benji.rewis@mongodb.com">Benji Rewis</assignee>
                                    <reporter username="milkie@mongodb.com">Eric Milkie</reporter>
                        <labels>
                    </labels>
                <created>Fri, 9 Dec 2022 13:38:18 +0000</created>
                <updated>Tue, 24 Jan 2023 17:07:57 +0000</updated>
                            <resolved>Wed, 11 Jan 2023 17:15:11 +0000</resolved>
                                                    <fixVersion>1.12.0</fixVersion>
                    <fixVersion>1.12.0-alpha1</fixVersion>
                                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="5106594" author="benji.rewis" created="Wed, 11 Jan 2023 17:15:11 +0000"  >&lt;p&gt;Given that users are running into this Go driver/Golang issue when using tools like &lt;tt&gt;mongorestore&lt;/tt&gt;, would it be possible to add a similar &quot;Potential DNS Issues&quot; section to the documentation for enterprise tools that rely on the Go driver with almost the same wording as our (now updated) documentation &lt;a href=&quot;https://github.com/mongodb/mongo-go-driver/blob/master/mongo/doc.go#L95-L103&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;? Thank you &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="5106581" author="xgen-internal-githook" created="Wed, 11 Jan 2023 17:11:44 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Benjamin Rewis&apos;, &apos;email&apos;: &apos;32186188+benjirewis@users.noreply.github.com&apos;, &apos;username&apos;: &apos;benjirewis&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/GODRIVER-2679&quot; title=&quot;Improve docs/message for &amp;quot;cannot unmarshal DNS message&amp;quot; error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;GODRIVER-2679&quot;&gt;&lt;del&gt;GODRIVER-2679&lt;/del&gt;&lt;/a&gt; Elaborate on DNS issues docs and confusing DNS error. (#1158)&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-go-driver/commit/c05cb8aea4a59fda1fffcc3324707bc3664e7ba0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-go-driver/commit/c05cb8aea4a59fda1fffcc3324707bc3664e7ba0&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5100898" author="benji.rewis" created="Mon, 9 Jan 2023 20:24:38 +0000"  >&lt;p&gt;Apologies for the delay. Here&apos;s a PR to elaborate on our documentation with more explicit workarounds and wrap the &lt;tt&gt;cannot unmarshal DNS message&lt;/tt&gt; error with a pointer to that documentation: &lt;a href=&quot;https://github.com/mongodb/mongo-go-driver/pull/1158&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-go-driver/pull/1158&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I&apos;ll follow up with another documentation ticket to make sure there&apos;s a similar &quot;Potential DNS Issues&quot; section on enterprise tools that use the Go driver under the hood once we&apos;ve finalized the messaging within the Go driver.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                                                <inwardlinks description="is documented by">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10257" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Documentation Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10250"><![CDATA[Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6jqv:s07w</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>