200M : Servers DNS address could not be found

[rumpleforeskin]

Evening all,

Not been able to use the internet very well for the last few hours, webpages are returning the error "www.insertwebsitenamehere.com server DNS address could not be found"

The network log on the superhub is populated with the following error "No Ranging Response received - T3 time-out"

As a workaround on my desktop I have changed the adaptor DNS setting to use googles DNS server, unfortunately this can't be done on the android/apple devices in the house so they are without any website access.

Virgins server status page shows no Broadband issues in my area (LU4)
Reseting the superhub has not fixed the problem.
The superhub has no option to set a DNS address.

Oddly I can ping virgins DNS server and get a 8ms response with no packet loss so maybe the Superhub is try to use a different address than 194.168.4.100?

I have been having this issue intermittently the last couple of days.

Any help would be appreciated

[Taf]

Any odd spikes if you set up a monitor on http://www.thinkbroadband.com/ping/monitors.html ?

[General Maximus]

Originally Posted by rumpleforeskin

As a workaround on my desktop I have changed the adaptor DNS setting to use googles DNS server, unfortunately this can't be done on the android/apple devices in the house so they are without any website access. The superhub has no option to set a DNS address.

Before I start my usual rhetoric I would like to say that the good news is that I don't think there is an actual fault with the dns server and it is more likely that your connection is flakey. I make that assumption because yours is the only post complaining about dns issues and if the server(s) were unavailable/gone down you would see everyone moaning their asses off.

That being said, it is not an excuse. Being able to specify the dns servers you want to use is one of the most basic features of all routers and VM have deliberately removed it in the shub so they can force you to use their own (one more troubleshooting step they don't have to worry about). As you have already eluded to, I have been using google's dns server for many year and never once had a single problem with availability. Although you may only experience dns issues once or twice, you are aware of the level of frustration that ensues when you essentially experience a loss of service. I will repeat many a previous assertion which is if you want to mitigate all these completely avoided oversights in the shub, put it in modem mode and buy a proper router.