# # This list is for people who want to double check that the DNS server # they're using while on the VPN is one of our DNS servers. # # These were once public servers, but we're phasing out public DNS because # there's too many vulnerabilities inherent in the DNS protocol that make # us more susceptible to distributed/reflected denial of service attacks, # and other forms of DNS related abuse. # # The Switzerland (190.211.255.227) server is the only one's still running # a public DNS server, but it will eventually be closed as well. # # Our DNSCrypt resolvers ( https://cryptostorm.is/cs-resolvers.md ) and # relays ( https://cryptostorm.is/cs-relays.md ) are still open to everyone, # and we have no plans to close those down in the foreseeable future. # If you're a customer of ours and you're trying to protect your DNS before # you connect to the VPN, use DNSCrypt. If you're not a customer of ours, # you can still use our DNSCrypt resolvers/relays to encrypt your DNS. Your # traffic helps obfuscate the DNS traffic generated by our VPN clients, # making it more difficult for DNS-based correlation attacks by whoever # may be listening. # # # This list is for people who want to double check that the DNS server # they're using while on the VPN is one of our DNS servers. # # These were once public servers, but we phased out public DNS because # there's too many vulnerabilities inherent in the DNS protocol that make # us more susceptible to distributed/reflected denial of service attacks, # and other forms of DNS related abuse. # # Our DNSCrypt resolvers ( https://cryptostorm.is/cs-resolvers.md ) and # relays ( https://cryptostorm.is/cs-relays.md ) are still open to everyone, # and we have no plans to close those down in the foreseeable future. # If you're a customer of ours and you're trying to protect your DNS before # you connect to the VPN, use DNSCrypt. If you're not a customer of ours, # you can still use our DNSCrypt resolvers/relays to encrypt/anonymize your DNS. # Your traffic helps obfuscate the DNS traffic generated by our VPN clients, # making it more difficult for DNS-based correlation attacks by whoever may # be listening. # # austria 94.198.41.235 2001:ac8:29:a1::53 # belgium 37.120.236.11 2001:ac8:27:103::53 # brazil 177.54.145.131 2804:391c:0:7::53 # montreal 176.113.74.19 2a0d:5600:19:5::53 # vancouver 196.240.79.163 2a02:5740:24:45::53 # czech 217.138.220.243 2001:ac8:33:77::53 # london 78.129.248.67 2001:1b40:5000:a2::53 # manchester 195.12.48.171 2001:ac8:8b:61::53 # finland 185.117.118.20 2a0c:f040:0:1924::53 83.143.242.43 2a0d:5600:142:11::53 # paris 163.172.34.56 2001:bc8:32d7:200c::53 # berlin 37.120.217.75 2001:ac8:36:61::53 # dusseldorf 89.163.221.181 2001:4ba0:ffed:76::53 # frankfurt 146.70.82.3 2a0d:5600:1d:9::53 # hungary 86.106.74.219 2001:ac8:26:61::53 # india 165.231.253.163 2001:470:1f29:204::53 # milan 217.138.219.219 2001:ac8:24:a1::53 # moldova 176.123.4.231 2001:678:6d4:5023::53 # netherlands 185.107.80.84 2a00:1768:6001:8::53 # norway 91.219.215.227 2001:ac8:38:94::53 # poland 37.120.211.91 2a0d:5600:13:71::53 # portugal 91.205.230.224 2a06:3040::ec4:53 # romania 146.70.66.227 2a04:9dc0:0:162::53 # serbia 37.120.193.219 2001:ac8:7d:47::53 # singapore 37.120.151.11 2a0d:5600:1f:7::53 # sk 108.181.50.218 2406:4f40:4:c::53 # barcelona 37.120.142.115 2001:ac8:35:17::53 # sweden 128.127.104.108 2a00:7142:1:1::53 # switzerland 190.211.255.227 2a02:29b8:dc01:2220::53 # sydney 37.120.234.251 2001:ac8:84:4d::53 # tokyo 146.70.31.43 2001:ac8:40:df::53 # la 195.206.104.203 2a0d:5600:4f:5::53 # dc 198.7.58.227 2604:9a00:2010:a0bb:6::53 # florida 146.70.240.203 2a0d:5600:6:123::53 # atlanta 130.195.212.211 2a0d:5600:145:5::53 # chicago 108.181.63.163 2604:6600:2700:b::53 195.242.212.131 2a0d:5600:144:1::53 # vegas 79.110.53.51 2a0d:5600:3:19::53 # newyork 146.70.154.67 2a0d:5600:24:54::53 # oregon 179.61.223.47 2605:6c80:5:d::53 # dallas 209.58.147.36 2606:9880:2100:a006:3::53 # seattle 64.120.5.251 2607:f5b2:1:a00b:b::53