I have a superhub, yet I cannot change the DNS settings for its DHCP server. I have looked through several of the posts here but have not found any that provide anything approaching a reasonable explanation for this puzzling decision. Can you explain why you have imposed this restriction on your customers?
The whole point if DHCP is so that you do not have to go to each device and set things like the DNS servers. I have never found a bit of networking kit before which did not allow you to set the DNS servers for DHCP and so I do consider this to be a restriction. Manually setting the DNS servers so it works in one location can just end up causing issues if you ever take that kit to a different location and so is just generally a bad idea. Using the local DHCP environment to set appropriate things such as DNS is a pretty widely accepted best practice.
What I am looking for is an explanation as to why VM decided to impose this restriction and if forcing extra work and effort onto its customers is a company policy or if they just made a foolish decision in this case.
I think you are missing the point. I understand how I can work around the issue, I already have. My question is 'Why?' - what led to this decision in the first place? Is it a case of deliberate policy to make it harder than it has to be and if so, why?, or was this just not something they considered a requirement? If the later, then maybe the policy can be reviewed and changed.
For instance, one reason might be so that VM can monetise NXDOMAIN lookups - if someone types in a domain name and misspells it, they are redirected to a page with a list of sponsored links. Thats fair enough, though I would then like to know how I can provide feedback which might get this policy reviewed with the potential to allow customers the option of changing the hub DCHP server settings. Call it a gesture of good will - after all, I've already worked around the issue and so they are not getting my misspelled lookups anyway. All it has succeded in doing so far is to make me put in extra effort whilst getting annoyed with them as a company.... and of course ranting in this forum ;-)
the SH is designed to be a very basic device to make it easyer to support and for non technical users to use. Changing the DNS server requires network knowledge so would not fall into what the SH was designed for. It was given modem mode to allow people that want more to use there own routers.
Its unlikey to change. Many viruses and malware now try and change routers DNS settings. This way that security risk is removed.
Sadly not a Virgin customer anymore.... Unless you want to cable my new street. my internet sucks.
I think you are missing the point. I understand how I can work around the issue, I already have. My question is 'Why?
Its not a work around VM have always offered their DNS to get you going just because they make a modem do NAT does not mean you can change DNS by NAT which NAT is not needed in a modem so it changes nothing and breaks more stuff for what you signed up for you either want a broken TCP/IP to have many devices or one WAN TCP/IP connection for the internet because when the time comes you will want the latter.
It is a basic ISP provided router, like sky and bit offer.
The settings have been simplified to allow the majority of home users access and change simple settings without getting overwhelmed with options.
As others have said, this is why Modem Mode was included in the recent firmwares, to allow users that want more complex options and steps to use their own modem and give them access to these more technical options
***** If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!! I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences. Office 365, Dynamics CRM and Cloud Computing Jedi