said by Sadachara:Actually, Bill's positive outlook isn't accurate.
WOW has been implicated in hijacking traffic in the past.. Google NebuAD - there were lawsuits involved with them hijacking traffic. WOW is also know to hijack via NXDOMAIN, and PAXFIRE servers.
WOW actually has a history of sniffing/intercepting, or contacting companies to do it.
»www.mediapost.com/public ··· uit.html
I do not believe this has anything at all to do with the OPs issue. We already know that WOW will send you to some advertising page if you use their servers and type in a bad name.
The thing with Google, Netflix, Akamai is different. These all can act as a CDN (Content Delivery Network). So if WOW has some google servers in their network the Google name server looks at the IP to see there the request is coming from. If it is from an AS that contains some Google servers, it returns those IPs which in this case belong to WOW.
When I worked at Chrysler we used Akamai to deliver content so a DNS lookup to a "chrysler.com" IP might get you an Akamai server IP instead of our IP and depending on where in the country you were, it could change. You get the closest one.
Here is my dig output:
[crypto@centmain ~]$ dig google.com +trace
; > DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2 > google.com +trace
;; global options: +cmd
. 516029 IN NS m.root-servers.net.
. 516029 IN NS e.root-servers.net.
. 516029 IN NS c.root-servers.net.
. 516029 IN NS d.root-servers.net.
. 516029 IN NS f.root-servers.net.
. 516029 IN NS i.root-servers.net.
. 516029 IN NS g.root-servers.net.
. 516029 IN NS l.root-servers.net.
. 516029 IN NS h.root-servers.net.
. 516029 IN NS a.root-servers.net.
. 516029 IN NS j.root-servers.net.
. 516029 IN NS b.root-servers.net.
. 516029 IN NS k.root-servers.net.
;; Received 228 bytes from 127.0.0.1#53(127.0.0.1) in 572 ms
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
;; Received 500 bytes from 192.33.4.12#53(192.33.4.12) in 947 ms
google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns4.google.com.
;; Received 164 bytes from 192.31.80.30#53(192.31.80.30) in 256 ms
google.com. 300 IN A 67.149.209.237
google.com. 300 IN A 67.149.209.223
google.com. 300 IN A 67.149.209.251
google.com. 300 IN A 67.149.209.224
google.com. 300 IN A 67.149.209.230
google.com. 300 IN A 67.149.209.244
google.com. 300 IN A 67.149.209.210
google.com. 300 IN A 67.149.209.245
google.com. 300 IN A 67.149.209.238
google.com. 300 IN A 67.149.209.231
google.com. 300 IN A 67.149.209.217
google.com. 300 IN A 67.149.209.216
;; Received 220 bytes from 216.239.34.10#53(216.239.34.10) in 51 ms
You see I go to the roots, then to Google and get back WOW IPs. I run my own BIND server.
Netflix/Google/Amazon need to have their content distributed all across the country so you can stream from the closest server else it would never work very well. This is how I understand these things to work if the ISP has local cache servers.