Newcamd client not connecting to all ports on server with dyndns hostname

= Revision All threaded OScam. >r3146

= Issue Description When connecting to a server that has a dyndns hostname rather than a static ip address using newcamd protocol not all ports are always getting card data.

If for example a oscam server has 3 cards, you will randomly get card data from maybe 2 of 3 ports sometimes and on the odd occasion you may get card information from all 3 ports.

If you enter the servers ip rather than the dyndns hostname into the client config this problem does not happen and all works perfectly. OScam oldstable also does not have this issue. I have tested with both MGcamd and Evocamd and the behaviour is exactly the same with both clients so it appears to be a OScam issue I think.

Server logs don't show anything so no point attaching them.

Client logs just show "(null)" for the port that has not recieved card data in MGcamd and Evocamd shows "connection error -4" for the same thing.

= When the issue occurs Randomly when connecting via newcamd client to a oscam server that is resolved by a dyndns hostname rather than its ip address.

= How the issue is reproducable Connect to a oscam server that has a dyndns hostname and several cards using a newcamd client e.g. MGcamd or Evocamd. You will observe that the client will not get card information from/log in to all ports.