Global Routing with Anycasted DNS. Teardown: NSONE
scalescale.com
Global Routing with Anycasted DNS. Teardown: NSONE
1–10 of 19 posts
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#2Hi- this is Chris from ScaleScale/MaxCDN. I wanted to thank Kris for making himself available for this. I'd be interested in hearing pros/cons about the format for ScaleScale so we can keep tweaking our posts. We have some more great ones planned very soon - your feedback will help make them more relevant.
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#3Kris from NSONE really knows his stuff. We are on process of moving all our DNS traffic to them. When starting to look into them I was skeptical of US ever using such a new provider... But their hands-on approach changed our minds...
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#4Great read and really does an awesome job showing not only the tech of what NSOne has built, but the 'why' behind the 'how'. DNS is such a deceptively simplistic service, but I think that's only due to the lack of real innovation in the space. NSOne is doing an awesome job changing that. Thanks @chris and @kris ;-)
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#5Hi- this is Chris from ScaleScale/MaxCDN. I wanted to thank Kris for making himself available for this. I'd be interested in hearing pros/cons about the format for ScaleScale so we can keep tweaking our posts. We have some more great ones planned very soon - your feedback will help make them more relevant.
Kris here. Thanks Chris for putting this together, it was a really fun set of questions. I think a lot of what makes NSONE different is the philosophy behind the tech. We're not a DNS company, we're a traffic management company and we think DNS is a great place to do traffic management. Hope that comes across in this article.
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#6Kris is a great guy and the team at NSONE are really solid.
Really good to see such a detailed article that addresses the topic from top to bottom.
I think more and more people are going to want to use something like this to build a global infra, especially across multiple providers. DNS is an often forgotten (other than everything being a 'fucking DNS problem' :-) part of the stack, and it's good to see a fresh approach.
Great article @mxpxrocks10
(disclosure: I was founder@Voxel and am investor@nsone, so my opinion is probably more than a bit biased ;-)
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#7Hi - great post, thanks. I had a question about the heat map. What is the /32s and 10Q, can you explain it some more please?
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#8Hi - great post, thanks. I had a question about the heat map. What is the /32s and 10Q, can you explain it some more please?
Hi -- glad you like the post. /32s are individual DNS resolver IPs we observed in each country from among the sample we took (half a percent of the traffic we saw during a 24h period).
The >10Q column is how many of those resolvers we saw that did >10Q from among our sample -- you can see there are many fewer resolvers that are doing even moderate amounts of traffic.
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#9Hi - great post, thanks. I had a question about the heat map. What is the /32s and 10Q, can you explain it some more please?
Hi -- glad you like the post. /32s are individual DNS resolver IPs we observed in each country from among the sample we took (half a percent of the traffic we saw during a 24h period). The >10Q column is how many of those resolvers we saw that did >10Q from among our sample -- you can see there are many fewer resolvers that are doing even moderate amounts of traffic.
Er -- I should have said, that did more than 10 queries from among our sample.
Re: Global Routing with Anycasted DNS. Teardown: NSONE
#10Earlier quoted context omitted.
Hi -- glad you like the post. /32s are individual DNS resolver IPs we observed in each country from among the sample we took (half a percent of the traffic we saw during a 24h period). The >10Q column is how many of those resolvers we saw that did >10Q from among our sample -- you can see there are many fewer resolvers that are doing even moderate amounts of traffic.
Er -- I should have said, that did more than 10 queries from among our sample.
that's a huge drop off, right?