OK, now what I can do with that info is run a 'reverse' NSLOOKUP using the IPs you posted and see where it returns the data to.
Now bear in mind that the way the internet works for me is different to the way it works for you. That's because you're on AOL who use (as far as I can tell) a different routing system to literally everyone else in the galaaxy and who, in my professional opinion, suck donkey balls.
That aside, here are my results for the reverse lookup:
66.220.152.32 - www-slb-11-09-frc1.facebook.com
2.18.190.196 - non-existent domain
77.91.249.30 - www.guardian.co.uk
212.58.244.69 - bbc-vip114.telhc.bbc.co.uk
The reason that the Facebook and BBC ones look different to what you typed in is that they have hundreds (in facebook's case, thousands) of domains and servers to handle all the traffic to their site.
The most important one here is the Santander one. This is being bounced to, as you can see, a domain that doesn't exist.
A check on the IP at the DomainTools website shows that it's managed by Akamai technologies, a company who bounce stuff around the internet. They're a legit company, and Santander seem to use them for their DNS management because when I run an NSLOOKUP for the Santander site, I get the IP 23.14.222.196, which, when I reverse the lookup, takes me to akamaiedge.net.
However, it is possible that this is a scrap of the DNS hijacking which is left over.
If you can copy and paste that HijackThis log, it would help immensely because that is likely to give me the info I need.