dns - Can you use Route 53's latency based routing in conjunction with Cloudflare? -
i've registered domain through route 53. records in route 53:
fakeelias.ca. #.#.#.# fakeelias.ca. ns brett.ns.cloudflare.com roxy.ns.cloudflare.com fakeelias.ca. soa ns-####.awsdns-17.org. awsdns-hostmaster.amazon.com. staging.fakeelias.ca. #.#.#.# www.fakeelias.ca. alias fakeelias.ca. (z1pgzi762j7wmn)
to cloudflare working in front of s3 buckets had replace ns entry cloudflare gave me , cname mappings buckets work through cloudflare.
what's not working paths fakeelias.ca, www.fakeelias.ca , staging.fakeelias.ca.
i want use latency based routing through route 53 fakeelias.ca point nearest nginx server. staging.fakeelias.ca point nginx staging server. ns entries cloudflare messing up? i'm kinda new dns stuff.
update 9/2016:
cloudflare has released traffic manager feature can global load balancing , health checks: https://blog.cloudflare.com/cloudflare-traffic-manager-the-details/
yes, can use cloudflare cdn edge/proxy , route53 routing behind it.
you need have 2 different domain names registered work, 1 route53 , other cloudflare.
setup route53 route queries servers want using record set (like routing.example.com pointing , europe servers). read route53 documentation details on how this.
setup cloudflare public domain want website , enter cname record pointing route53 domain name setup above. cloudflare's servers follow cname , routed right server using route53 rules.
each cloudflare datacenter lookup , cache dns responses locally geographic routing work fine.
even if aren't using cloudflare proxy traffic site, there still benefits in using them
- cloudflare's dns servers of the fastest means less latency , better performance users.
- if have lots of traffic, cloudflare save money since have pay lookups cached cf servers, while free dns service takes care of rest.
- dns has lots of security risks , using cloudflare dnssec features can make sure domain isn't damaged or redirected while being protected ddos (which can happen dns too) , other issues.
i used setup both geographic load balancing (sending closest server) global round-robin (spreading load randomly) on service doing billions of requests month , worked well.
Comments
Post a Comment