UK - Virgin

[Staff 9972]

Dozens of reports throughout 2014 and 2015 show that in Virgin network DNS poisoning is (probably intermittently) used against https://airvpn.org

 

Solution: use a publicly accessible, not poisoned DNS, for example OpenNIC https://opennicproject.org or contact us to know alternative domain names to access various https front ends in our infrastructure.

[Ernst89 11]

Assuming you mean Virgin Media UK. How did you determine this?

 

Why would they mess with DNS to the web site rather than routing to the actual OpenVPN servers? 

 

Its a nice web site but not even that important to AirVPN users who only actually need it for initial setup.

 

This is a curiosity only question as the solution of using an alternative DNS doesn't seem to have any downsides.

 

 

[Staff 9972]

Assuming you mean Virgin Media UK. How did you determine this?

 

 

We cross-checked the reports of dozens of our customers with Virgin Media UK, asking them to resolve "airvpn.org" on two of Virgin DNS servers. Since all the reports matched exactly throughout one year, we can safely assume that the reports are reliable. It is also worth mentioning that DNS poisoning of airvpn.org is intermittent, and when contacted directly about the issue, Virgin Media responded to us that it was a technical problem, totally unintentional.

 

 

 

Why would they mess with DNS to the web site rather than routing to the actual OpenVPN servers? 

 

How are we supposed to know? All in all even the cyber workers of the government of China are interested in our web site, not only with DNS poisoning but also IP blocking. Who knows, maybe it's really just an obscure technical error that re-occurs periodically.

 

Kind regards

[rainmakerraw 94]

Virgin Media also throttle OpenVPN, and have done for years. Connecting via Eddie (or Viscosity, or NetworkManager) over UDP:443 gives a hard 1MB/sec cap. Switching to SSL:443 or SSH:22 gives full throughput speeds even to the same Air server.