Disabling DNS Rebind attack protection on Hub 3

[lriley06]

I use my Hub 3 in modem mode, with a Pfsense box as my router. I have my own internal hostname for the Hub 3 to avoid having to type the IP address in each time I need to access it. I used to be able to access the web interface via this hostname, rather than typing the IP. Presumably, Virgin have pushed a new update to the Hub 3, as I now just get redirected to a rebind_warning.html page with the contents "DNS REBIND ATTACK" when using the hostname, and the only to access without this is via IP. Is there any way to disable this behaviour?

[lriley06]

Don’t really want to test this as I don’t think it would make any difference and also obviously makes my internet go down for a bit while I test it.

It’s certainly annoying as this used to work perfectly, and I can’t think of any change that would make it stop working.

Can anyone else replicate this issue with modem mode, just to double check it’s not an issue with me?

[legacy1]

Well if you don't test we can't blame it on a VM firmware update.

[lriley06]

I honestly don’t think connecting my computer instead of my router to the hub 3 is going to make this error go away. I’ll try it later tonight though. Thanks for your help!

[lriley06]

Just come back from holiday and found some time to test it. Connected Mac mini directly to Hub 3, got public IP via DHCP and was able to ping 192.168.100.1. Could also ping modem.test but accessing http://modem.test in web browser redirected me to the same page - http://192.168.100.1/rebind_warning.html.

Just tried accessing the same page via https (so https://modem.test) and found that this actually worked, and I didn't get a redirect! Accessing the admin interface via https takes a stupidly long amount of time to load though, even compared to the already slow http version, so not brilliant. Also, the default localhost.localdomain certificate that is used for https access is not trusted by my computer, and also isn't valid due to modem.test not being in the Common Names list. Is there any way to attach my own certificate issued by my trusted root CA, instead of the default certificate?

Thanks so much for all of the help!

[legacy1]

So we can blame VM or at least the one doing the firmware now its unlikely going to change not sure why someone would go to the trouble of doing this.