Our infrastructure page will show you that
BuddyNS is a global cluster with presence in all of these regions:
- Middle East
How do we select each location?
We manage geographical presence as a strategic asset, and latency is a crucial
factor in our planning. Users have
patience for loading time, and all the time you save on DNS is more room for your
web servers to generate valuable content: simple improvements on DNS save you otherwise
substantial costs in development and infrastructure. Now, it won't make much difference
if such latency is 25ms, 5 or 10, but growing that past 100ms certainly does.
Most DNS resolvers today select the DNS server to query based on best response time,
so having points of presence nearby can reduce latency substantially. Our locations
are planned with the goal to offer sub-30ms response time to densely populated areas
and sub-70ms to most of the world's connected areas.
Why haven't we deployed to South America and Africa? South America generally lacks
intra-regional peering, so that most traffic between South American countries goes
through Miami and back, making local deployments mostly useless. Africa's
ring backbone has a similar
For users to whom jurisdictional borders are relevant, notice that BuddyNS provides
you with this information explicitly.
Which locations should you use? We instruct users to delegate their zones to
3-5 BuddyNS servers. This improves reliability and resolution time,
since most Internet resolvers pick their destination based on response time.
Our setup docs help you select which BuddyNS
servers you should delegate to, based on your location.