The ISPвЂ™s recursive DNS resolver replies to the end-user with an IP address for As you can see from the described process, the authoritative DNS server does not see the end userвЂ™s IP address, but the IP address of the userвЂ™s DNS resolver.The DNS server replies with the IP address of.The DNS resolver iterates through requests to the authoritative DNS server for the В zone (assuming it does not have cached reply for this entry if it does, see step 4 below).

This step involves sending a DNS query to the configured DNS resolver (usually the one, which the ISP provides) The user opens a browser or starts the Dropbox desktop client which attempt to resolve DNS record of our IP address.In the picture below you can see how users are mapped to our edge PoPs. With geolocation-based load balancing, the вЂњclosestвЂќ PoP is indeed the one which is closest in terms of distance from the user. For different users, we reply with different IP addresses. LetвЂ™s try to decipher this statement: being sent in this context means that when a user is doing DNS request, we would reply with a specific Dropbox IP address. The idea behind this approach could be simply described as sending the user to our closest point of presence. In our previous post about the D ropbox edge network, we were talking about geolocation-based load balancing. By co-developing the platform capabilities with NS1 to handle these outliers, we deliver positive Dropbox experiences to more users, more consistently. This article describes our work with NS1 to optimize our intelligent DNS-based global load balancing for corner cases that we uncovered while improving our point of presence (PoP) selection automation for our edge network. The Dropbox Traffic team is charged with innovating our application networking stack to improve the experience for every one of our users-over half a billion of them.

Load shotpro from dropbox