This has been happening for several months now and I’ve lost patience.
Every so often I get plagued by DNS errors (dns_probe_finished_no_internet and dns_probe_finished_nxdomain), if I disconnect and reconnect to the WiFi I can browse but then 2 minutes later I’ll have to do the same thing.
This will go on for an hour or so at a time then it’ll be fine. It happens across all devices but I mainly use my laptop while on the VM WiFi
Things I have tried, and none have solved it:
- using command prompt and all the standard commands like ipconfig/flushdns, netsh/winsockreset etc etc
- manually setting DNS Server to Google / Cloudflare etc, same thing happens eventually
-powering off and on, and latterly factory resetting the router (SuperHub2)
-turning off all firewalls / antivirus
If it was persistent or restricted to one device I’d think it was the device but I’m just wondering if this is to do with the router
Here are the stats – clearly can’t get a status when the DNS isn’t working:
Welcome to our forums and thanks so much for your first post - so sorry that you're having some issues with your broadband.
We're always grateful when a customer posts there logs, so thanks for popping them on our wall for us.
As our lovely VIP @ravenstar68 has advised, your logs do indicate that you have some issues on your upstreams - I have been able to locate your services from here and been able to confirm we are seeing the same errors.
However, before we can go any further and potentially book a technician or new Hub, we can see that it has been over a month since your Hub has been rebooted.
Please can you go ahead and reboot the hub for me? Once we can confirm that this has been done, I can go ahead and go through the rest of the diagnostics and see what we need to do to get you back up and running again 🙂
There are some further checks we may need to do with your channels but I don't want to make those changes before the reboot has refreshed the system.
We're also seeing high numbers of T3 - Usually indicating upstream issues and T4 - usually indicating downstream issues - timeouts.
I rather suspect we're looking at upstream noise on channels 2,3 and 4 as high power levels on the upstream indicates that the hub is having trouble talking to the CMTS and is shouting to make itself heard. I think that if we left it channels 4 and 3 will creep up closer to 51.0 dBmV as well. Normally the channels transmit levels have to match to a certain degree as well as if they are too far out we get a Dynamic Range Window Violation - but the levels aren't disparate enough to cause this at the moment.
As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.
Thanks for taking the time to post on the forum and welcome to the community. Disappointing to hear of the broadband issues but thank you for posting all of the additional information and to ravenstar68 for looking over this for us.
It does seem to be something we need to take a closer look at so I'm going to send you a private message to get some additional details from you.
Looking forward to hearing back form you to get the ball rolling.