Same, its very often too.
I've logged it with the host; let's see what they come back with.
Guys, next time this happens for you, can you run the following on cmd:
nslookup onemoreinthetolly.com
tracert onemoreinthetolly.com
... and paste the results here as soon as you're able.
Ta
Or PM or email me them. I don't mind.
I've noticed it happens during particular times during the day. For the past week I haven't been able to load the page during the morning but it resolves itself by evening.
Pepe LeFrits wrote: Guys, next time this happens for you, can you run the following on cmd: nslookup onemoreinthetolly.com tracert onemoreinthetolly.com ... and paste the results here as soon as you're able. Ta
Err... sorry Pepe, what does that mean? Will get you a screen shot too.
Start -> Run -> cmd
Clearly some of you just need to get the message that you're not wanted.
Especially Gael.
Haha. You tried to get rid of me again last night:
Sorry, forgot about running those tests though. Made a note of them now to remind me next time.
Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Calum>nslookup onemoreinthetolly.com Server: dns4.nottingham.ac.uk Address: 128.243.42.59 Non-authoritative answer: Name: onemoreinthetolly.com Address: 207.58.171.181 C:\Users\Calum> C:\Users\Calum>tracert onemoreinthetolly.com Tracing route to onemoreinthetolly.com [207.58.171.181] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 10.1.165.253 2 1 ms <1 ms 1 ms 10.4.254.77 3 1 ms 1 ms 1 ms 10.2.1.1 4 1 ms 3 ms 1 ms 128.243.253.218 5 1 ms 1 ms 1 ms uon1-gw-gi3-1.emman.net [195.195.228.249] 6 1 ms 1 ms 1 ms kmc1-gw-v314.emman.net [195.195.228.89] 7 3 ms 3 ms 3 ms so-0-2-0.leed-sbr1.ja.net [146.97.42.9] 8 7 ms 8 ms 8 ms as3.lond-sbr1.ja.net [146.97.33.98] 9 8 ms 8 ms 8 ms ae13.lond-sbr4.ja.net [146.97.33.134] 10 58 ms 7 ms 8 ms ae0.lond-gw-ixp4.ja.net [146.97.35.182] 11 8 ms 9 ms 9 ms 195.66.224.185 12 84 ms 84 ms 85 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54 .43.57] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * 93 ms 94 ms vl3901.na41.b003328-0.dca01.atlas.cogentco.com [ 66.28.65.218] 17 87 ms * 88 ms 38.104.30.102 18 88 ms 88 ms 88 ms 209.50.254.14.servint.net [209.50.254.14] 19 88 ms 88 ms 88 ms sc-smv2088.servint.net [207.58.153.210] 20 88 ms 88 ms 89 ms snow.wiredstorm.com [207.58.171.181] Trace complete.
Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Calum>nslookup onemoreinthetolly.com Server: dns4.nottingham.ac.uk Address: 128.243.42.59
Non-authoritative answer: Name: onemoreinthetolly.com Address: 207.58.171.181
C:\Users\Calum> C:\Users\Calum>tracert onemoreinthetolly.com
Tracing route to onemoreinthetolly.com [207.58.171.181] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.1.165.253 2 1 ms <1 ms 1 ms 10.4.254.77 3 1 ms 1 ms 1 ms 10.2.1.1 4 1 ms 3 ms 1 ms 128.243.253.218 5 1 ms 1 ms 1 ms uon1-gw-gi3-1.emman.net [195.195.228.249] 6 1 ms 1 ms 1 ms kmc1-gw-v314.emman.net [195.195.228.89] 7 3 ms 3 ms 3 ms so-0-2-0.leed-sbr1.ja.net [146.97.42.9] 8 7 ms 8 ms 8 ms as3.lond-sbr1.ja.net [146.97.33.98] 9 8 ms 8 ms 8 ms ae13.lond-sbr4.ja.net [146.97.33.134] 10 58 ms 7 ms 8 ms ae0.lond-gw-ixp4.ja.net [146.97.35.182] 11 8 ms 9 ms 9 ms 195.66.224.185 12 84 ms 84 ms 85 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54 .43.57] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * 93 ms 94 ms vl3901.na41.b003328-0.dca01.atlas.cogentco.com [ 66.28.65.218] 17 87 ms * 88 ms 38.104.30.102 18 88 ms 88 ms 88 ms 209.50.254.14.servint.net [209.50.254.14] 19 88 ms 88 ms 88 ms sc-smv2088.servint.net [207.58.153.210] 20 88 ms 88 ms 89 ms snow.wiredstorm.com [207.58.171.181]
Trace complete.
This has been happening regularly, but as mentioned, only at my work. Name resolution / routing output attached.
The issue causing this should be fixed within the next couple of hours. Let me know if it still happens.
Let me know if it still happens.
Still happens at my work Pepe. Same issues as previously.
fu burnsy.
Heh. Sorry mate. To be honest it's only work and I can still reach the site on my phone, so I'm not bothered. Our global network is a joke as well.
Pepe LeFrits wrote: The issue causing this should be fixed within the next couple of hours. Let me know if it still happens.
Seems to be working well lately for me. So thanks. Will let you know if it resurfaces.
This issue still arises for me, but less frequently and for shorter periods.
Haven't noticed an outage of more than an hour or so for a while.
