Adrian Ivan

Here are my fist findings: - the HA strategy seems to be one main instance with backup eureka servers - the clients are provided with a list of eureka servers...

Hi again, I am pleased to announce that the behaviour from the previous post happens because all my Eureka nodes were configured with localhost as host name. Changing to peer1...

``` eureka: client: registerWithEureka: true fetchRegistry: true useDnsForFetchingServiceUrls: true eurekaServerDNSName: eureka.local eurekaServerPort: 8761 eurekaServerURLContext: eureka ``` The settings above definitely do the trick for me.

I did not test multiple zones though. Please come back and share your results for your multiple zones setup.

Never tested multiple zones. In one single zone (defaultZone) I could configure multiple servers and they saw eachother as replicas. How are your clients configured?

i would start with the default region(don't try to set it yet) and default zone and see if the dns config is ok. It is ok when in the Eureka...

``` availabilityZones: us-east-1: us-east-1a,us-east-1b ``` My hunch is that for the client you should specify one single zone, after all the client runs in a single zone, isn't it?

Actually, i think your issue is that you specify availabilityZones. you should leave that to the dns.

datacenter=cloud?

Arthur, maybe you need to read the docs a bit, and the source code.