OK, so explain how by just changing the DNS the route sudenly becomes less congested???
I'm not sure how else to explain it for you. The Destination IP adress changes. The Destination Server changes. The Destination server locaion is changed. The route to that new server has potentially changed. Verizon CAN STILL SEE you're IP address (the source) and the destination IP address.
Go play around on some Looking Glass traceroutes for a while. Do traceroutes to "amazon.com" and change the location (source server)
https://www.sprint.net/lg/lg_start.php
http://lookingglass.level3.net/traceroute/lg_tr_main.php
Here's some examples on DNS for "amazon.com"
Provider~~~~~Src Location~~Dest IP
----------------------------------------------------------
Sprint~~~~~~~Wash, DC~~~72.21.194.212
Sprint~~~~~~~Miami, FL~~~72.21.215.232
Level3~~~~~~Miami, FL~~~~72.21.215.232
XO~~~~~~~~~Miami, FL~~~~205.251.242.54
Level3~~~~~~Tampa, FL~~~72.21.215.232
VZ FiOS~~~~~Tampa, FL~~~176.32.98.166
VZ Business~~Dallas, TX~~~205.251.242.54
VZ FiOS~~~~~Dallas, TX~~~~72.21.194.212
And so forth. Verizon still sees you're IP and the Dest IP. You just are using another DNS to give you some other IP for a Server which is somewhere else. Unlocator might differentiate it's DNS by pursuing the Video streaming market such as Netflix and Amazon and spend time scouring for IP addresses and destination servers for these services. Verizon could blacklist all these IPs.
Verizon could do something as simple and USE ARIN list to block, throttle, limit, or shape entire ranges of systems: