|
|
|
|
|
by bullen
1676 days ago
|
|
Sure you get more downtime, that's why I have 2x fibers with my 100% read uptime database between them, that way both fibers have to go down at the same time for existing customers to be unable to login. I noticed DNS was a bit slow on first lookup, it's not a big deal for my product and well worth the extra control. I looked up anycast, and it's unclear how you enable that if you have your own DNS servers, I have 3, one in each continent but I'm pretty sure the DNS provider I use does not use the DNS in the right region! Is that something you tell the root DNS servers about through your domainname registrar? You would think this had been built into the root servers ages ago? They can clearely see where my DNS servers are!? |
|
Have you measured this from another continent? I noticed it could add quite a bit of latency, especially when the remote client has a relatively slow internet connection.
More specifically, I noticed that when I was using a CNAME to a domain with DNS in the US.
To use anycast, you need the same IP addresses in multiple locations. Realistically, you can only do that if you peer with local ISPs and can advertise a route.
I never dug enough to start my own ISP, so it's a bit fuzzy for me, but I think you need to control your own AS (or partner with one), and announce your routes over BGP from multiple areas.
Most CDN or cloud providers probably offer anycast as an option, and it is likely the default configuration for their DNS as well as static websites.