ip - WCF service binds at 0:0:0:0 instead of dns alias -


we have cluster wcf services running resource each in separated resource group. these groups have dns alias named there cap name e.g. appqa en appprod each ip's 10.110.250.1 , 10.110.250.2.

actually it's same wcf service running on baseadresss, example of our baseadress:

<add baseadress="net.tcp://appqa.domain.com:4504/....   ,   <add baseadress="net.tcp://appprod.domain.com:4504/....  

but when running these services on same node noticed getting errors there address in use.

we found weird because added our alias in base address section nslookup of both our aliases , gave both right ip address.

when running prod service, did telnet command ip address of qa , 4504 port. able make connection means running on both ip adresses (or addresses , port 0:0:0:0:4504).

as test changed our baseadresses

<add baseadress="net.tcp://10.110.250.1:4504/....  <add baseadress="net.tcp://10.110.250.2:4504/....  

and can run both services next each other on same node, prove our services work dns resolution not work.

it works in when enable port sharing don't want because of different sla.

has idea how can force wcf use ip address of dns alias?


Comments

Popular posts from this blog

sublimetext3 - what keyboard shortcut is to comment/uncomment for this script tag in sublime -

java - No use of nillable="0" in SOAP Webservice -

ubuntu - Laravel 5.2 quickstart guide gives Not Found Error -