Serving GEO specific IP numbers – geoDNS provider

When it comes to speed for websites, the topic covers a wide range to think about. From the structure of your website code to the optimizations of your images and delivery order of the single elements on the page and finally to the technological setup.

My friend Bastian Grimm from Germany has been talking about these topics for years and you can find more like his excellent German presentation on Slideshare – just search for site speed.

This short blog post focusses on one technological aspect: The way of the data to the user.

There are CDN offers out there, like, who we used in some projects and who offer a quick “on demand” solution, if you need a CDN now. Then there is CloudFlare. We love CloudFlare, who act as a mediator that you plug in between the user and your website. They come with a CDN and optimization methods included. But if you build your own network, there was always the question about the DNS services, which could help you to distribute your traffic easily.

Screenshot 2016-05-23 12.51.17

For those administrators out there, who work on global networks: The combination of SQUID (or nginx) as a reverse proxy and the Amazon Web Services (AWS) Route 53 is fantastic. I have that implemented for a customer recently and the results are very nice in terms of distribution and speed improvements.

Here is a screenshot of the registration of a new Geo-sensitive answer in the AWS console:


As you can see above, you can easily add destinations on a global scale and even by country in that powerful backend. That service was finally the tipping point for me to go AWS in the first place. Very nice! In combination with simple reverse proxies and this service, it is very easy to distribute your traffic in a way to speed up your answer times tremendously!

Leave a Reply