15 Oct
2013
15 Oct
'13
1:34 a.m.
On Mon, 2013-10-14 at 17:12 -0400, Coy Cardwell wrote:
...Two servers, both sharing the same database.
Server1, Server2. Both servers
are behind a NAT (AWS).
If I set the DNS to return both IP addresses for the domain on the A
record, everything works, all is well.
If I set the DNS to return values based on latency and the Calling Client
gets Server1's IP Address but the Receiving Client is registered to
Server2, the call fails from a timeout. I can see the attempt to go through
at the packet level and a 'non-local' socket message as well.
If the DNS returns Server2's IP Address and the Receiving Client is
registered to Server2, the call completes...
Thanks.
- Coy Cardwell
Hi Coy,
Can you explain the scenario a bit in regards to sharing the same
database across the two servers? I can be a problem for the local client
to try to receive a call from a server that they're not registered to.
--fred
Fred Posner, @qxork