Discussion in 'Site Feedback' started by burninbush, May 12, 2010.
Well that's sortly what I said, isn't it. Anywho, I hope this silences the whiners once and for all.
SHUT THEM DOWN, we hope it does!! Fraggin whiners!
Yeah, whiney little frags. Fraggy frags.
Further data: timed-out multiple attempts to connect this morning at ~9:30 my time.
Got there fairly quickly just now. I have been watching messages lately when visiting the site, and the delay looks to be 'searching for site name' -- once connected, it moves along OK unless I stay in one place for a long time, then I get the searching delay again. DNS?
Edit: slow again this morning [tues 6/15] ~5:10am -- 'looking for www.ranch...' even got that switching between threads
Big trouble just now, had to go trough google !!!!
very peculiar....i've had zero probs getting to the site...
I couldn't get on many times from work, home and the PC at the club the past day. Three PC's, many aborted log-in's, very strange.
Yep bad day to get to the site, one thing of note Dan, I tried and got the screen some people get can't find ya, hit back on the browser after I went back to
google and I got in...
Apparently Google ( I had to abandon all my principles to do this) sends you to a cache of the site when the DNS fails, explaining why it appears you get in using Google when the DNS is down.
As the DNS failures are usually limited to a few minutes, using the cache can create the illusion of being on the site as the DNS is likely to be up when you make a post.
Had a hard time getting here had to go thru google and even there i had to try several times
Timed-out 9 times this morning at around 9:50am my time.
It's been purring like a kitten here, all dang day...
root@mepis-xp2400:~# traceroute www.ranchero.us
traceroute to www.ranchero.us (126.96.36.199), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.477 ms 1.712 ms 2.185 ms
2 c-98-210-24-1.hsd1.ca.comcast.net (188.8.131.52) 10.614 ms 15.354 ms 20.555 ms
3 te-7-1-ur02.hayward.ca.sfba.comcast.net (184.108.40.206) 20.763 ms 20.899 ms 21.028 ms
4 te-0-8-0-6-ar01.oakland.ca.sfba.comcast.net (220.127.116.11) 21.804 ms 21.934 ms 22.057 ms
5 pos-0-5-0-0-cr01.sacramento.ca.ibone.comcast.net (18.104.22.168) 23.928 ms 24.062 ms 24.180 ms
6 pos-1-10-0-0-cr01.losangeles.ca.ibone.comcast.net (22.214.171.124) 33.487 ms 28.186 ms 20.696 ms
7 pos-0-12-0-0-cr01.dallas.tx.ibone.comcast.net (126.96.36.199) 59.985 ms 65.409 ms 65.839 ms
8 pos-0-2-0-0-pe01.1950stemmons.tx.ibone.comcast.net (188.8.131.52) 66.850 ms 66.978 ms 67.108 ms
9 theplanet-cr01.dallas.tx.ibone.comcast.net (184.108.40.206) 65.596 ms 65.874 ms 65.995 ms
10 te7-1.dsr02.dllstx3.theplanet.com (220.127.116.11) 66.500 ms te7-1.dsr01.dllstx3.theplanet.com (18.104.22.168) 177.828 ms te9-1.dsr02.dllstx3.theplanet.com (22.214.171.124) 66.215 ms
11 * * *
12 po2.car01.dllstx4.theplanet.com (126.96.36.199) 56.642 ms po1.car01.dllstx4.theplanet.com (188.8.131.52) 56.708 ms 56.314 ms
13 42.72.1343.static.theplanet.com (184.108.40.206) 63.156 ms 66.492 ms 66.313 ms
bb:> working well at this moment. I'll try this again when it fails next.
thats all greek to me
The first line is the only one you need during this issue. It's caused by failure of the DDNS so your traceroute will fail at step one and say it's unable to resolve the host. I believe the hosting provider is aware of this and may or may not be interested in fixing it.
thats all greek to me >5.0
It's not Greek, it's Geek. Network admins talk that stuff. Me, just barely.
You can see the command "traceroute" given at top -- literally traces and shows the chain of connections to get from my desktop to the server at ranchero.us., and how quickly each of them acknowledges a 'ping'. Less time is better.
When the chain is blocked for some reason, you may at least be able to see where it got to before it failed. Do it enough times and you can get a clue where the block is located. Internet Protocol ["IP"] is supposed to route a packet around a blockage in the middle of the chain -- obviously can't do that for the first or last ends.
The first line is the only one you need during this issue. It's caused by failure of the DDNS so your traceroute will fail at step one and say it's unable to resolve the host. >Geek
Uhmmm ... well, if you say so. But previous traceroute checks here have timed-out almost all the way there. I'll try it again when I can't get through next.
I have seen the 'unable to resolve' message coming from the FF browser.
Ok I am computer stupid but I have a link on my toolbar (AOLHELL) and I use it to get to the site I never have any problems getting to the site???
It dose not go to the main page
Every once in a very blue moon will experience a couple of timeouts and then will get in. Didn't happen for me today from 0230 PDT (time adjusted for the convenience of folks on the left coast) through when bb posted his dissatisfaction with the site.
Bill has talked to them a few times about it, not sure that there is much he can do except find a different hosting site which is probably more Rancherobuck$$$$$$$$$$ out of his pocket. Be patient, nothing earth/life changing happens here that can't wait another few seconds/minutes or so.
Be patient, nothing earth/life changing happens here that can't wait another few seconds/minutes or so. >72gtva
Hmmm, I'm 71 -- please don't tell me to be patient.
Separate names with a comma.