A cluster resolver implementation that assumes that Eureka cluster configuration is provided in two level,
cascading DNS TXT records. The first level shall point to zone level DNS entries, while at the zone level
server pools shall be provided (either CNAMEs or A records).
If no TXT record is found at the provided address, the resolver will add 'txt.' suffix to the address, and try
to resolve that address.
Example
Lets assume we have a service with root domain myservice.net, and a deployment in AWS us-east-1 on all three zones.
The root discovery domain would be:
DNS record |
TXT record content |
txt.myservice.net |
txt.us-east-1a.myservice.net
txt.us-east-1b.myservice.net
txt.us-east-1c.myservice.net
|
txt.us-east-1a.myservice.net |
ec2-1-2-3-4.compute-1.amazonaws.com
ec2-1-2-3-5.compute-1.amazonaws.com
|
txt.us-east-1b.myservice.net |
ec2-1-2-3-6.compute-1.amazonaws.com
ec2-1-2-3-7.compute-1.amazonaws.com
|
txt.us-east-1c.myservice.net |
ec2-1-2-3-8.compute-1.amazonaws.com
ec2-1-2-3-9.compute-1.amazonaws.com
|