Hi all I wonder if someone can help, I suffered an area outage on Wednesday 20th Jan 2021 in my area (DA11), this was for BB and TV, service resumed the following day, but for the last week I've experienced really slow web browsing on all my devices whether wired or wireless. I did the usual checks of restarting the router etc.
After a period of diagnosis I've worked out the issue, as the title suggests DNS.
I have my devices set to use cloudfare DNS, 22.214.171.124 - this is set on the devices as I use the SH3 as modem and router. Speed from the service is as expected - 100mb.
When I reverted back to using VM DNS services the pages load instantly, I then checked by changing to other cloud provider such as google, 126.96.36.199 and browsing was slow again. This was not the case before the service outage so expect some routing has gone amiss.
Who can I speak to in VM to get this sorted the 1st level tech guys are going through the normal restart everything set back to factory settings.
When you have your dns configured to use google/cloud flare, what happens when you open a command prompt and use nslookup?
To test, open a command prompt, type nslookup and hit enter... you should get a new > prompt. Above the > prompt it should say default server 188.8.131.52 or something similar.. then just type in a dns name and hit enter - does it time out, does it come back instantly, what happens?
Hi tehwolf , using nslookup I receive a resolution to any dns servers and websites, as the pages do subsequently load its more of a routing issue (i.e. taking too long) I also did some traceroutes to 184.108.40.206 and 220.127.116.11 both see timeouts along the hops. I can post these to see if others see similar.
Tracing route to one.one.one.one [18.104.22.168] over a maximum of 30 hops:
1 2 ms 2 ms 1 ms 192.168.0.1 2 10 ms 9 ms 9 ms 10.53.35.241 3 9 ms 15 ms 9 ms basl-core-2b-xe-815-0.network.virginmedia.net [22.214.171.124] 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 19 ms 18 ms 17 ms 86.85-254-62.static.virginmediabusiness.co.uk [126.96.36.199] 8 18 ms 16 ms 17 ms ldn-b1-link.telia.net [188.8.131.52] 9 26 ms 30 ms 20 ms ldn-bb4-link.ip.twelve99.net [184.108.40.206] 10 31 ms 26 ms 33 ms dln-b2-link.ip.twelve99.net [220.127.116.11] 11 27 ms 31 ms 29 ms cloudflare-ic-310815-dln-b2.c.telia.net [18.104.22.168] 12 28 ms 27 ms 26 ms one.one.one.one [22.214.171.124]
Tracing route to dns.google [126.96.36.199] over a maximum of 30 hops:
1 2 ms 2 ms 1 ms 192.168.0.1 2 13 ms 9 ms 7 ms 10.53.35.241 3 11 ms 9 ms 9 ms basl-core-2b-xe-716-0.network.virginmedia.net [188.8.131.52] 4 * * * Request timed out. 5 15 ms 17 ms 17 ms eislou2-ic-1-ae3-0.network.virginmedia.net [184.108.40.206] 6 22 ms 17 ms 16 ms 6-14-250-212.static.virginm.net [220.127.116.11] 7 21 ms 21 ms 20 ms 18.104.22.168 8 17 ms 15 ms 21 ms 22.214.171.124 9 18 ms 17 ms 21 ms dns.google [126.96.36.199]
Tracing route to cache1.service.virginmedia.net [188.8.131.52] over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.0.1 2 12 ms 11 ms 16 ms 10.53.35.241 3 29 ms 16 ms 17 ms basl-core-2b-xe-716-0.network.virginmedia.net [184.108.40.206] 4 9 ms 17 ms 7 ms cache1.service.virginmedia.net [220.127.116.11]
So, the nslookup shows that there’s no issue between you and the name servers you’re trying to use..
My windows knowledge is a bit rusty, but AFAIK the only difference between nslookup and your browser doing a lookup is that nslookup queries the dns server directly whereas a “normal” lookup will first check whether the dns name is the computers own name, then it will check the hosts file, then it will query the dns server
my knee jerk would be a device issue, but you say it’s affecting all of the devices on your network? What other devices is it affecting?