Ongoing DNS Issues? Timeouts....

[#1]

I swear, some PN staff post / work from home

[#2]

Switched to opendns - all good for now - cheers TORPC / npr

[#3]

I work 9-5:30.  Well, that's what my contract says anyway

[#4]

I suppose asking for overtime / & or a raise, is out the question

[#5]

My internet speed over the past two days has been shocking, so slow that websites just won't load. Get it sorted Plusnet 

[#6]

Just changed to openDNS and working a treat now!? 

[#7]

Changed to open dns and tried tracert to PN

does this indicate that 195.166.128.197 is having issues?

C:\Users\Alan>tracert www.olus.net (mistyped plus.net, but obviously still an actual address)
Tracing route to www.olus.net [67.215.66.132]
over a maximum of 30 hops:
 1     3 ms     2 ms     1 ms  192.168.0.1
 2     *        *        *     Request timed out.
 3   214 ms   155 ms    39 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
 4    82 ms    55 ms    40 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.15
4]
 5    26 ms    26 ms    32 ms  xe-4-3-0.ptw-cr02.plus.net [212.159.0.246]
 6    36 ms    26 ms    53 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
 7    72 ms    33 ms    65 ms  te-4-2.car5.London1.Level3.net [217.163.45.249]
 8   112 ms    35 ms    46 ms  ae-2-52.edge6.London1.Level3.net [4.69.139.108]
 9    29 ms    27 ms    70 ms  OPEN-DNS-IN.edge6.London1.Level3.net [195.50.116
.54]
10    42 ms   130 ms    26 ms  hit-servfail.opendns.com [67.215.66.132]
Trace complete.
C:\Users\Alan>tracert www.plus.net
Tracing route to portal.plus.net [212.159.9.2]
over a maximum of 30 hops:
 1     9 ms    14 ms     1 ms  192.168.0.1
 2     *        *        *     Request timed out.
 3   155 ms   120 ms   132 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
 4    32 ms    27 ms    27 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.15
2]
 5    26 ms    26 ms    26 ms  xe-4-3-0.ptw-cr01.plus.net [212.159.0.244]
 6    26 ms    27 ms    27 ms  ae1.pcl-cr01.plus.net [195.166.129.1]
 7    27 ms    26 ms    37 ms  po2.pcl-gw01.plus.net [195.166.129.41]
 8    35 ms    51 ms    34 ms  gi5-8.ptp-cr01.plus.net [84.93.224.48]
 9    36 ms    35 ms    39 ms  vlan2658.ptp-elb02.plus.net [84.93.224.45]
10    34 ms    37 ms    34 ms  portal.plus.net [212.159.9.2]
Trace complete.
C:\Users\Alan>
direct from router:
Tracing route to www.plus.net [212.159.9.2] over a maximum of 20 hops
1    *      *      *      Request timed out.
2 39ms 124ms 130ms   195.166.128.197
3 25ms 25ms 25ms    212.159.2.152
4 25ms 25ms 25ms    212.159.0.244
5 25ms 25ms 33ms    195.166.129.1
6 65ms 25ms 25ms    195.166.129.41
7 32ms 32ms 33ms    84.93.224.48
8 33ms 33ms 34ms    84.93.224.45
9 33ms 33ms 33ms    212.159.9.2
Trace complete.

[#8]

No, it's fine.  Its just busy routing traffic instead of responding to your ping.
Think of it this way, the ping which hit 67.215.66.132 went through that server and back in 42ms so its fine

[#9]

Cheers.

Need to look up how this all works.

[#10]

We've made a change in the network which may help for any one connected to a PCL gateway.  Anyone still watching connected via PCL and using our DNS?

[#11]

Do you know what change(s) has been made ?

[#12]

Yep!
We've just applied the changes to the PTN/PTW half of the platform now.  Again, yell if that has improved or not.
Hold that thought...

[#13]

Kelly, I've changed back from OpenDNS to your DNS and I appear to be getting the same quality of connectivity on your DNS now as I was getting on OpenDNS.

[#14]

Brill.  What gateway are you on?
http://usertools.plus.net/@gateway

[#15]

DNS errors for the last half hour or so - seem ok again for now (same yesterday, different time)