How to sort out DNS problems properly
Virgin Media's SuperHub is only useful for one thing: Ethernet to Cable modem bridging. Hardware-wise it's a pretty normal Netgear 802.11n router using a Broadcom chipset which is pretty much run of the mill and OK. However, VM's 'custom' firmware practically bricks the box.
I don't use either VM's DNS servers nor do I use spoofing DNS providers like OpenDNS or Google (spoofing means if a DNS record fails it shows a page of ads by redirecting). Instead you should use a non-spoofing (or ideally, a DNSSEC) upstream DNS server. Locally on your LAN you should also use either a full (Bind / Windows with Active Directory) or a caching proxy DNS (dnsmasq) server.
DNSSEC is sort of like SSL for DNS - not so much encryption, but means the record isn't spoofed. Because spoofing DNS is easy it's normally the first thing ISP's like VM roll out to do their blocking of pr0n/piracy stuff.
There is a more honest use of spoofing that OpenDNS and Google employ by providing you with a more useful page (read ads) when a DNS query fails.
Either way, your laptop is having to talk to a server miles away that may or may not be spoofing your DNS, in order to find the IP address of each and every image and page in a web page. So don't use any of them: use your own DNS server, with trustworthy upstream DNS servers.
Upstream servers don't need to be super fast, because the speed is being covered by your local DNS server - the upstream DNS servers just need to be reliable and honest.
Sound complicated it really isn't.
So how to do this:
a) If you already use Active Directory (e.g. you log onto Windows with Ctrl+Alt+Delete), then you already have a DNS server. Configure your PDC and BDC's DNS servers (which are a requirement for AD) with decent upstream DNS servers and tell the DHCP Server to use the PDC and BDC for clients.
b) If you have a QNAP/Synology NAS, they also have DNS server capabilities.
c) If you have a spare machine or a VM able to use exclusive use of NICs for WAN connections, then install pfSense, and bobs your uncle.
d) If you only have a bog standard router, try to use DD-WRT and make use of it's dnsmasq server.
e) If you're still out of luck, there are plenty DNS servers available for Windows that run as a service or in the task tray.
The point is they're plenty available, and you will notice an immediate speed up of your browsing (particularly on Mac OS X / iOS) when using it.
So which DNS servers to use? Most people will say use Google (126.96.36.199 / 188.8.131.52) or OpenDNS (184.108.40.206 / 220.127.116.11). However, as I mentioned, they spoof DNS anyway (Google does support DNSSEC though).
The ideal servers to use are entirely dependent on your location, because the absolute fastest DNS servers will be the ones with the fattest low latency pipes to you. Thankfully, someone made a tool to do exactly that: DNS Benchmark.
1) Download Steve Gibson's DNS Benchmark: https://www.grc.com/dns/benchmark.htm. No need to install, like any proper software, just run it.
2) Open it and click 'Nameservers' tab
3) Right-click on the main list of servers, check 'Test DNSSEC Authentication'
4a) If you've used DNS Benchmark before, skip to step 5. Otherwise click the 'Add/Remove' button
4b) Click 'Rebuild Custom List' at the bottom, and click the new button also called 'Rebuild Custom List'.
4c) Wait about 40 minutes for the tool to sort through about 4200 DNS servers.
5) Go back to the 'Nameservers' tab, click 'Run benchmark'
6) Once complete, select the fastest servers you want to use - if you want DNSSEC-enabled servers, they are marked green.
A DNS Server on your network should have 2-4 upstream DNS servers. Usually when they don't have a record in their local cache, they'll request from all 4 upstream servers simultaneously and return the first successful result. Most clients will just choose the first one.
And with that, you have fast and authentic (if you use DNSSEC servers) DNS solution locally and no Virgin Media snafu's that even when it's working 'normally' it's broken.