AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Due to this mistake, only part of the VPN server addresses were included in the allowed list. On November 22 at 9:14 UTC, a new version of the management service was deployed that contained an error. This list is formed by a management service that knows all the IP addresses of all the VPN servers. AdGuard DNS servers periodically request an updated list of IP addresses for which the rate limit should be disabled. To work around this problem, we remove the rate limit for VPN servers. The rate limit is quite low, and some popular AdGuard VPN locations generate more requests than allowed. This is a standard tactic to prevent DNS amplification (i.e., using a public DNS server to perform DDOS attacks on a third party). By using a popular public DNS server (such as AdGuard DNS), you are sharing the same server as tens or hundreds of millions of other Internet users.ĪdGuard DNS employs rate limiting to restrict the number of requests a user can send to the DNS server. We believe this is not the best tactic, and matching your IP address with your DNS server's address can be a signal of using a VPN. Normally, VPN services use the same VPN server as your DNS server. Why do we do this? The goal is to make you 'less noticeable' among Internet users. It's always DNSīy default, AdGuard VPN users use AdGuard DNS Non-Filtering as their DNS server. We apologize for this outage and would like to provide more information about its causes and the steps we are taking to prevent such issues in the future. Primarily affected were users in locations such as Frankfurt, Amsterdam, London, and Dallas. On November 22, 2023, there was a disruption in the AdGuard VPN service that may have caused Internet access issues for a significant number of users.
0 Comments
Read More
Leave a Reply. |