coredns icon indicating copy to clipboard operation
coredns copied to clipboard

Route53 not support Failover

Open icyxp opened this issue 3 years ago • 1 comments

aws route53 supports failover, but not work in coredns route53 plugin

route53 failover config:

s-search-hdfs-nn.test.release | A | Failover | Secondary | 10.60.8.187 10.60.0.129 10.60.11.82
s-search-hdfs-nn.test.release | A | Failover | Primary | 10.60.13.249 10.60.6.242 10.60.12.249

The domain name is resolved on the eks node as follows:

# nslookup s-search-hdfs-nn.test.release
Server:		10.60.0.2
Address:	10.60.0.2#53

Non-authoritative answer:
Name:	s-search-hdfs-nn.test.release
Address: 10.60.13.249
Name:	s-search-hdfs-nn.test.release
Address: 10.60.12.249
Name:	s-search-hdfs-nn.test.release
Address: 10.60.6.242

But the result of resolving the domain name in the pod is as follows:

nslookup s-search-hdfs-nn.test.release
Server:         172.20.0.10
Address:        172.20.0.10#53

Name:   s-search-hdfs-nn.test.release
Address: 10.60.8.187
Name:   s-search-hdfs-nn.test.release
Address: 10.60.0.129
Name:   s-search-hdfs-nn.test.release
Address: 10.60.11.82
Name:   s-search-hdfs-nn.test.release
Address: 10.60.13.249
Name:   s-search-hdfs-nn.test.release
Address: 10.60.6.242
Name:   s-search-hdfs-nn.test.release
Address: 10.60.12.249

icyxp avatar Jun 17 '21 03:06 icyxp

@icyxp thanks for the report. We can potentially support it but probably with standalone healthchecks only, not alias+evaluate_target_health. Can you provide terraform or some other description of your aws config?

dilyevsky avatar May 08 '22 04:05 dilyevsky