4 ms·
Don't use them for DNS, just point 60 second TTL A records at them.
by 0xEFF 6y ago
Don't use them for DNS, just point 60 second TTL A records at them.
- phire 6y agoI don't think cloudflare supports such a configuration. The DNS is part of the load balancing, they serve different IPs based on location of the DNS query. Edit: Apparently they do support a CNAME configuration if you pay for one of their business plans. That gives you the option to quickly switch away (if your TTL is low enough) but will impact performance by having to fetch the CNAME every 60 seconds.
- EE84M3i 6y agoDoes cloudflare actually do geo-loadbalancing via DNS A records now? For years they only did anycast, unlike, say, Akamai, which hands out different IPs for each POP.
- phire 6y agoActually, I'm not sure if they do any DNS geo-loadbalancing. I've seen it report different IPs from different locations at times, but that could be something else. But I'm pretty sure they use DNS do other loadbalancing and DDoS mitigations. For example, if a site is under attack, they can send it to different IP addresses to keep it away from other sites. Or if someone is directly targeting a cloudlflare IP with a DDoS, they can redirect all sites to other IPs and just blackhole that IP.
- jniedrauer 6y agoWhere do you put your DNS servers? On-prem is going to be less reliable than cloudflare which has a 100% uptime SLA. I doubt your local ops team can compete.
- jonplackett 6y agomy thoughts exactly. still none the wiser what the solution is.