Local DNS suffix is now cable.virginm.net
4 days ago I received and setup my Virgin Hub 3. I then put the Hub 3 into modem only mode and connected this to my Linksys Velop mesh WiFi router. Everything was working fine until the early hours...
Forum Discussion
The Hub in modem mode is just a bridge, so the Parental and Virus stuff does not work in anycase as this is bypassed by your own Router. Just double check your Hub 3 is actually in modem mode? I would be tempted to do a full 60 second pinhole reset on the Hub and put it back in modem mode afterwards. This should all be done with a direct wired connection.
Your Linksys should be setup with the DNS of your choice and this should replicate to all your connected devices.
60 second factory pinhole reset as below;
Remove any ethernet cables from the Hub and hold the pinhole reset switch for 60 seconds. Do NOT reboot the Hub, just let it do it's thing. Note you will need the passwords from the bottom of the Hub afterwards, so make sure they are legible. NOTE this will remove any custom settings you may have set in the Hub, and they will all have to be setup again.
I've tried the restart and I am still seeing some of my devices responding with hostnames that end in .cable.virginm.net although many of them seem to be also responding to pings on <hostname>.local as well as <hostname>.cable.virginm.net