title: Amazon Elastic Load Balancer (ELB) url not resolved by instance attached to it
body: <p>We are using Amazon Web Services EC2 to create two servers which are then attached to an Elastic Load Balancer (ELB). The instances eventually use the url of the load balancer itself to request WCF services.</p>
  
  <p>In few situation an instance is not able to resolve the load balancer’s url for 10 minutes of  so, and then it work fine. Here in summary is what we do :</p>
  
  <ol>
  <li>We create a load balancer </li>
  <li>We create two instances in the same zone</li>
  <li>We connect the instances to the load balancer and we wait for them both to be ready (ie able to process request).</li>
  </ol>
  
  <p>Sometime an instance attached to the load balancer is not able to resolve the load balancer’s url once we start the testing. After about 10 minutes is then able to resolve the name.  Here is the error we are getting:</p>
  
  <blockquote>
    <p>---> System.Net.WebException: The remote name could not be resolved: 'nightlyblb13083105564592203800-455163519.us-east-1.elb.amazonaws.com'</p>
  </blockquote>
  
  <p>Any idea ? We added all the checks to make sure that both instances are ready once we start using the load balancer and we are pretty confident that this is the case, however the problem described above happen about 1 out of 20 tests.</p>