I can't remember but Windows probably still uses the WINS protocol for internal networks and doesn't need DNS for peer to peer networking. Most home networks didn't have any DNS server access before the advent of t'internet.
Windows will use broadcasts by default, same on 95 through to Windows 8.1 - this works for home networks as people don't have routers. WINS is not needed as this is for broadcasts over routers. (ie a kludge!).
However once you get into real modern windows networking (e.g. corporate) then Windows DOES use DNS - either its own, or BIND on a *NIX machine - broadcasts can be disabled and WINS is never installed unless you have NT 4 SP2 or earlier still.
Changing to any ISP DNS on a home network works because home networks use short names, such as ping familyroom instead of ping familyroom.myhome.local - and most home users expect to be able to browse or just enter a UNC such as \\familyroom\printer
One way to fix the issue would be to set up your own DNS / DHCP server and then you can turn off DHCP on the HomeHub. However its often easier to buy a decent router and put the HH in a cupboard for when you need to call BT support.
James -
plusnet unlimited fibre - 2 Jun 14 - 470m - Sync 55/9.4 (BT was 51/9.8)
15 years broadband (1999 ntl:cable trial) - Asus RT-AC68U with HG612 - PN BQM - PN speed - old BT speed