title: WCF service binds at 0:0:0:0 instead of dns alias
body: <p>We have a cluster where to WCF services are running as a resource each in a separated resource group. These groups have a dns alias named to there cap name e.g. APPQA en APPPROD each with an IP's 10.110.250.1 and 10.110.250.2. </p>
  
  <p>Actually it's the same WCF service but running on another baseadresss, like this example of our baseAdress: </p>
  
  <pre><code>&lt;add baseAdress="net.tcp://appqa.domain.com:4504/.... 
  
  and 
  
  &lt;add baseAdress="net.tcp://appprod.domain.com:4504/.... 
  </code></pre>
  
  <p>But when running these services on the <strong>same</strong> node we noticed that we were getting errors like there is Address is in use. </p>
  
  <p>We found that weird because we added our alias in the base address section a nslookup of both our aliases and that gave us both the right IP address. </p>
  
  <p>When running only the PROD service, I did a telnet command to the IP address of the QA and the 4504 port. I was able to make a connection this means that we are actually running on both IP adresses (or all addresses and port like 0:0:0:0:4504). </p>
  
  <p>As an extra test we changed our baseadresses to  </p>
  
  <pre><code>&lt;add baseAdress="net.tcp://10.110.250.1:4504/.... 
  &lt;add baseAdress="net.tcp://10.110.250.2:4504/.... 
  </code></pre>
  
  <p>And then we can run both services next to each other on the same node, so we prove that our services work only the dns resolution does not work. </p>
  
  <p>It all works in when we enable port sharing but we don't want do that because of a different SLA.</p>
  
  <p>Has someone a idea how we can force WCF to use the IP address of his dns alias?</p>