Jump to content
|Topic||Stats||Last action by|
|Take a look at your Google Dashboard Location History.||
|April 2015 Desktops||
|I made the mistake of deploying Onedrive For Buisness||
|Grand Theft Auto V||
|Latest Nvidia GPU driver comes with support for linux kernel 4.0!||
Posted 04 October 2012 - 19:16
Posted 04 October 2012 - 23:25
No and here’s why.
and the 3rd option may well be, because my ISP has full control over this "SuperHub" firmware, it is so locked down you can't change the DNS yourself when you wish to use your own, I reckon that the reason why DNS servers are not been provided in Modem mode is because the DNS servers are in fact hard coded into the firmware of the SuperHub itself. (Virgin Media can send firmware updates out to the SuperHub whenever they want and it will automatically update once plugged in).
Posted 05 October 2012 - 16:37
No and here’s why.
In modem mode nothing is hard coded and in fact you don't get DNS and DHCP by the hub in this mode it is at another end point beyond the hub.
As for the hub in router mode having DNS hard coded that could be true however your device will still be able to override what DNS you wish to use.
And that is odd that VM DNS is not being sent out by DHCP.....
Posted 05 October 2012 - 17:06
Posted 05 October 2012 - 17:16
Posted 05 October 2012 - 17:24
If he double natted his connection and put his hub in router mode, and then connected his router his issue would be gone - because the cisco router would use the hub lan IP as its dns - and the hub in router mode would forward to what seems to be a hard coded dns server(s)?? Since clearly his ISP is not handing it out via dhcp.
What super hub firmware are you on? It's the buggiest pos ever but is usually fine in modem mode... Just tell them it keeps freezing and they should send you a new one
Posted 05 October 2012 - 21:03
Posted 06 October 2012 - 10:56
Posted 06 October 2012 - 11:00
Posted 06 October 2012 - 11:05
What does the SH have to do with they are not handing out dns via dhcp -- would not matter what modem he uses.
Its not really a problem, he could always just set dns -- where its a issue is that he can not tell his router what dns to use to lookup the ciscofqdn it wants to lookup. Because its limited to only setting it via dhcp on the wan interface.
I don't get why they don't hand out dns via dhcp - every other isp I have ever seen hands out this info. Why are they not, would seem to be an issue on this scope - because someone else said they are using the same isp and they get dns via dhcp.
Posted 06 October 2012 - 11:12
Posted 06 October 2012 - 14:04
Cable modems don't dish out the client IP that are WAN IP or the gateway or the DNS servers the cable modem is just a means to convert DOCSIS to Ethernet this applies to any and all cable modems or in the case of the super hub only when its in modem mode.
In both cases the cable modem would dish out the client IP, gateway details, DNS servers, etc.
Posted 06 October 2012 - 14:14
Posted 06 October 2012 - 14:21
Posted 06 October 2012 - 14:31
so your clearly coming off a different dhcp scope if your getting a different netblock for your IP before you got a 77.98 address with no dns.
Is it the same dhcp server? Curious before it was 188.8.131.52, I would send the sniffs you did showing that server was not sending dns in its options.
But now that you have it working shouldn't be a problem - I would assume most of their users are using their product for their routers so highly unlikely too many other users running into the issue you found.