<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 25 21:28:57 CDT 2013

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 add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/MB-746/MB-746.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[MB-746] DNS lookups don&apos;t work on Windows</title>
                <link>http://www.couchbase.com/issues/browse/MB-746</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>If I try to join another node by specifying the hostname of the server instead of using dotted decimal I get an error message saying:&lt;br/&gt;
&lt;br/&gt;
&amp;#39;Attention - Failed to resolve address for &amp;quot;windows&amp;quot;. The hostname may be incorrect or not resolvable. &amp;#39;&lt;br/&gt;
&lt;br/&gt;
I am able to run the following command from cmd.exe:&lt;br/&gt;
C:\Program Files\NorthScale\Developer Kit\bin&amp;gt;nslookup windows&lt;br/&gt;
Server:  speedtouch.lan&lt;br/&gt;
Address:  10.0.0.1&lt;br/&gt;
&lt;br/&gt;
Name:    windows.lan&lt;br/&gt;
Address:  10.0.0.28</description>
                <environment>Operating System: Windows&lt;br/&gt;
Platform: All</environment>
            <key id="10755">MB-746</key>
            <summary>DNS lookups don&apos;t work on Windows</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="2" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/critical.png">Critical</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="-1">Unassigned</assignee>
                                <reporter username="trond@northscale.com">Trond Norbye</reporter>
                        <labels>
                        <label>1.6.0-release-notes</label>
                        <label>1.6.5.3-release-notes</label>
                    </labels>
                <created>Sun, 14 Mar 2010 06:59:09 -0500</created>
                <updated>Sun, 5 Jun 2011 21:02:45 -0500</updated>
                    <resolved>Thu, 19 May 2011 11:50:26 -0500</resolved>
                            <version>1.6.4</version>
                                <fixVersion>1.7 alpha 1</fixVersion>
                                <component>UI</component>
                                <votes>0</votes>
                        <watches>6</watches>
                                                    <comments>
                    <comment id="13156" author="trond@northscale.com" created="Sun, 14 Mar 2010 07:00:00 -0500"  >Created an attachment (id=161)&lt;br/&gt;
log</comment>
                    <comment id="13157" author="trond@northscale.com" created="Sun, 14 Mar 2010 07:00:34 -0500"  >(version  is 0.9.3 devkit)</comment>
                    <comment id="13158" author="trond@northscale.com" created="Sun, 14 Mar 2010 12:19:39 -0500"  >this looks like 320, please verify</comment>
                    <comment id="13159" author="matt@northscale.com" created="Sun, 14 Mar 2010 12:50:22 -0500"  >I remember MB-204, but it was a different issue.  The resolution on 320 had to do with the way we were dropping in and installing erlang I believe.&lt;br/&gt;
&lt;br/&gt;
In any event, I will try some hostname resolution after getting through BAT right now.  I&amp;#39;m confident menelaus is doing the right thing, but there may be a case that erlang isn&amp;#39;t handling.&lt;br/&gt;
&lt;br/&gt;
This may be P3able, if it only resolves when using fqdn.  Did you try that by chance?</comment>
                    <comment id="13160" author="steve.yen@northscale.com" created="Sun, 14 Mar 2010 15:14:20 -0500"  >per discussion with rod, to P3 for 1.0.</comment>
                    <comment id="13161" author="dustin@sallings.org" created="Wed, 17 Mar 2010 10:23:59 -0500"  >Moving open bugs from 1.0 to later.</comment>
                    <comment id="13162" author="steve.yen@northscale.com" created="Thu, 3 Jun 2010 23:23:58 -0500"  >Aliaksey, I think this should be probably fixed &amp;quot;for free&amp;quot; as part of delayed IP addr assignment enhancement.</comment>
                    <comment id="13163" author="alkondratenko@gmail.com" created="Fri, 4 Jun 2010 07:57:02 -0500"  >Not sure. I&amp;#39;ve been using hostnames instead of addresses since cluster joining was working. And at least on linux erlang is resolving names via libc name service switch facility (i.e. usual gethostbyname, not some kind of home brewed async DNS resolver), so that mDNS names (like epsilon.local) work too.&lt;br/&gt;
&lt;br/&gt;
So this should be something win-specific, I guess.</comment>
                    <comment id="13164" author="alkondratenko@gmail.com" created="Wed, 22 Sep 2010 11:42:32 -0500"  >I need this tested on windows.</comment>
                    <comment id="13165" author="perry@northscale.com" created="Fri, 24 Sep 2010 07:22:23 -0500"  >Assigning to our QA department for testing.  Thuan, can you check this out specifically on Windows?</comment>
                    <comment id="13166" author="azhuravlyova@gmail.com" created="Fri, 24 Sep 2010 07:42:36 -0500"  >The issue is reproduced. &lt;br/&gt;
Node with names w2008x64qa.altoros.corp or w2008x64qa were not added though the node is accessible through web using this names. &lt;br/&gt;
UI error: Attention - Could not connect port mapper at &amp;quot;w2008x64qa&amp;quot; (tcp port 4369). With error Reason nxdomain. This could be due to firewall configured between the two nodes.&lt;br/&gt;
&lt;br/&gt;
Log is attached.</comment>
                    <comment id="13167" author="azhuravlyova@gmail.com" created="Fri, 24 Sep 2010 07:43:44 -0500"  >Created an attachment (id=648)&lt;br/&gt;
log</comment>
                    <comment id="13168" author="alkondratenko@gmail.com" created="Fri, 24 Sep 2010 09:08:01 -0500"  >erlang on windows clearly has issue with name resolution:&lt;br/&gt;
&lt;br/&gt;
Erlang web shell 0.01 (dennis:&lt;a href=&apos;mailto:killme2008@gmail.com&apos;&gt;killme2008@gmail.com&lt;/a&gt;)&lt;br/&gt;
1&amp;gt; inet:gethostbyname(&amp;quot;google.com&amp;quot;).&lt;br/&gt;
{error,nxdomain}&lt;br/&gt;
2&amp;gt; inet:gethostbyname(&amp;quot;localhost&amp;quot;).&lt;br/&gt;
{ok,{hostent,&amp;quot;localhost&amp;quot;,[],inet,4,[{127,0,0,1}]}}&lt;br/&gt;
3&amp;gt; inet:gethostbyname(&amp;quot;gwwin.altoros.corp&amp;quot;).&lt;br/&gt;
{error,nxdomain}&lt;br/&gt;
&lt;br/&gt;
pinging from cmd.exe to gwwin.altoros.corp and google.com works.</comment>
                    <comment id="13169" author="perry@northscale.com" created="Tue, 28 Sep 2010 20:48:06 -0500"  >Raising the priority of this since DNS seems broken on Windows.</comment>
                    <comment id="13170" author="alkondratenko@gmail.com" created="Wed, 29 Sep 2010 07:30:29 -0500"  >&lt;a href=&quot;https://support.process-one.net/browse/EJAB-860&quot;&gt;https://support.process-one.net/browse/EJAB-860&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
CC-ing Dmitry</comment>
                    <comment id="13171" author="sean@northscale.com" created="Thu, 30 Sep 2010 17:43:31 -0500"  >There&amp;#39;s no time to fix name resolution on Windows - this problem is not specific to us and there&amp;#39;s not an easy fix.</comment>
                    <comment id="13172" author="trond@northscale.com" created="Thu, 30 Sep 2010 18:37:58 -0500"  >If this is an Erlang bug, is it reported upstream ?</comment>
                    <comment id="13173" author="alkondratenko@gmail.com" created="Thu, 30 Sep 2010 18:57:42 -0500"  >See see my link on ejabberd bug report. It has links to upstream bug report and discussion.</comment>
                    <comment id="18558" author="perry" created="Tue, 16 Nov 2010 15:16:11 -0600"  >The Erlang link seems to indicate that this issue is fixed.  Can we import that into our Erlang?</comment>
                    <comment id="18559" author="perry" created="Tue, 16 Nov 2010 15:17:48 -0600"  >tagged: releasenotes</comment>
                    <comment id="18991" author="perry" created="Tue, 7 Dec 2010 18:41:14 -0600"  >Not sure why this was closed, it needs to remain open as the problem is not fixed.</comment>
                    <comment id="19490" author="perry" created="Fri, 28 Jan 2011 02:13:57 -0600"  >A Pivotal Tracker story has been created for this Issue: &lt;a href=&quot;http://www.pivotaltracker.com/story/show/9309683&quot;&gt;http://www.pivotaltracker.com/story/show/9309683&lt;/a&gt;</comment>
                    <comment id="19580" author="sean" created="Mon, 7 Feb 2011 21:07:56 -0600"  >We can use ejabberd&amp;#39;s fix for this.</comment>
                    <comment id="20102" author="aaron" created="Wed, 20 Apr 2011 12:57:56 -0500"  >Native resolver works on windows now. Registry hack not necessary since we only need to look up A and AAAA records.</comment>
                    <comment id="20623" author="perry" created="Tue, 10 May 2011 17:34:13 -0500"  >Perry Krug deleted the linked story in Pivotal Tracker</comment>
                    <comment id="20839" author="perry" created="Thu, 19 May 2011 11:48:15 -0500"  >Reopening to edit</comment>
                </comments>
                    <attachments>
                    <attachment id="10144" name="log.txt" size="707242" author="trond@northscale.com" created="Sun, 14 Mar 2010 07:00:00 -0500" />
                    <attachment id="10145" name="ns-diag-20100924103614.zip" size="49795" author="azhuravlyova@gmail.com" created="Fri, 24 Sep 2010 07:43:44 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Sun, 14 Mar 2010 12:50:22 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10010" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                <customfieldname>Flagged</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10010"><![CDATA[Release Note]]></customfieldvalue>
    
                </customfieldvalues>
            </customfield>
                                                                                                                                                <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>1381</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                                                                                        <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>