Looking a little deeper into this I suspect VM Smart Security has been silently enabled on the VM DNS of our account. We have a Hub 3 in Router mode & use the default VM DNS via DHCP.
Earlier I said the IP propagation to the VM DNS had yet to occur, was I totally wrong ?
Here is the NSLOOKUP first with VM DNS ( browser fails to work ) then with Google DNS ( browser works ).
C:\Users\Philip>nslookup www.hobbymaker.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Non-authoritative answer:
Name: www.hobbymaker.com
Addresses: 2a02:8801:200:1::1
81.99.162.48 ( What actually is this IP ? Who own it ??? )
C:\Users\Philip>nslookup www.hobbymaker.com dns.google
Server: dns.google
Address: 8.8.4.4
Non-authoritative answer:
Name: www.hobbymaker.com
Addresses: 2606:4700:10::6816:3ca7
2606:4700:10::ac43:170e
2606:4700:10::6816:3da7
104.22.60.167
104.22.61.167
172.67.23.14
Seeing this I concluded that as the Google DNS worked, the VM DNS was slow to update.
Look what happens when we reverse the process with the IP 81.99.162.48 a new host name is returned by the VM DNS. Try the same via Google DNS and the IP is unknown.
C:\Users\Philip>nslookup 81.99.162.48
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Name: lang-sspiprxy.network.virginmedia.net
Address: 81.99.162.48
There are no DNS records for IP 81.99.162.48 or for lang-sspiprxy.network.virginmedia.net
so Virgin Media are blocking www.hobbymaker.com by directing the browser to dummy IP / host.
Looking at lang-sspiprxy.network.virginmedia.net does the ss mean Smart Security ?