And, of course, it supported all known DNS protocols with out-of-the-box encryption. Rewritten in Go, AdGuard DNS gained the ability to handle high load and work with servers geographically dispersed around the world. We've changed the technology and the implementation approach. But it helped us finally make the decision to completely rewrite the service and take it much more seriously. This was probably the longest AdGuard DNS outage ever. I frantically tried to fix the situation, but could hardly do anything because of the terrible connection quality. I'll never forget one night when I was taking the train to my hometown to visit my parents, AdGuard DNS stopped handling the load due to too many users. And as the number of users grew, it became clearer that everything we did had to be thrown out and redone. A task that seemed very simple at first glance turned out to be much, much more difficult in reality. After all, you can't just take two weeks and make a high-quality service.
It took us only about two or three weeks to do everything from start to finish, post the announcement, and launch the service.
The first version of AdGuard DNS was written in Java, using existing developments from AdGuard for Android. That's when we had the idea of creating a DNS service as a way to get to the next level.ĪdGuard DNS was born as a completely experimental project that we didn't plan to spend much effort on.
It appeared at a time when AdGuard versions for all major platforms had already been released and we were trying to figure out how to protect from ads and trackers devices on which AdGuard could not be installed. It's hard to believe, but on July 26 AdGuard DNS turned 6 years old. Let's follow the journey that AdGuard DNS has made from a half-baked experimental project to a full-fledged product with more than 50 servers in 15+ locations. A lot has happened in this time – and I have so much to tell you. This is a big moment for us, which we have been steadily moving toward since 2016.
0 kommentar(er)
