That's weird. A Cincinnati native (Adam F) isn't having any problems, yet, I'm at work in Cincinnati, and I can't get on.

 

Just worked for me.
First time I was on that site too.

 

I wonder how much longer it will take NC to get access? We get everything last....

 

Well, it works now (one AM), so imagine it must really be up. I, on the othe hand, shouldn't be.

 

I believe it has to do with your ISP not what area you live in.

 

Speaking of which, where do you wheel? I'm going to get back down to Livingston sometime soon. That place is paradise!

 

I've only wheeled a few times at a friends farm. I'm just getting into the sport. I've signed up with KYTTORA. They've only had one run, which I missed, and it was at Livingston. There and the gorge/slade are the only fairly local spots. There's also the new KAOP in Eastern KY and a new park down in Harlan.

 

Still down for me as of 10:33 am EST 4/15

 

Still down for me here at work, but it worked at home last night.

 

http://www.tacomaterritory.com/forum

It's up.

 

This is where that last link takes me:

http://underconstruction.networksolutions.com/

 

If it's still not working for you, try the following:
Close all browser windows (IE and FireFox keep their own name cache)
Drop to a command prompt (START:RUN "CMD" <ENTER>)
Type IPCONFIG /FLUSHDNS
Restart your browser and try hitting the site.
If that still doesn't work, go back to a command prompt and type:
PING WWW.TACOMATERRITORY.COM
Copy the text from the command window and paste into this thread.
(It's okay if it times out, what we're looking for here is the IP address the name is resolving to - right now, it works for me and I'm getting 209.209.29.210)

 

I couldn't get on here at work yesterday, then last night at home I could get to the first page but nowhere else. Shortly thereafter it seemed to work fine again, but my this morning I had nothing, and still have nothing.

IP I got when pinged: 216.168.224.53
100% loss

 

That's the problem. It looks like when NetSol put up that page to let the world know the domain registration had expired they changed the DNS back to their own systems (to see this, run TRACERT 216.168.224.53 at a command prompt) and the proper record isn't getting propagated back out to the internet properly - almost like the NetSol record had a large TTL (a long time before it expires and your DNS server would to to the root DNS server to see if anything had changed with this record)

What this means is the TTORA site may have some problems until this gets cleared up or until they get it cleared up.

Right now, the TTL for the proper DNS record is 60 minutes - meaning the DNS server you ask to resolve names to IPs will go back to its source for that data every hour to see if it has changed).

Did you flush your DNS cache? (IPCONFIG /FLUSHDNS at command prompt after closing all IE windows)

You can check to see what the TTL is on the record you have by going to a command prompt and typing:
NSLOOKUP
SET DEBUG
WWW.TACOMATERRITORY.COM

The last line you see in the output should read TTL = xxx (xx min, xx sec) That will give you an idea of how long this could go on...

I'm not familiar with the TTORA site but if someone is, or knows their IT personnel, they might want to drop a friendly note about this problem.

 

It timed out and gave me nothing, but if I can remember to put pants on in the morning I am in good shape, I geuss I will take your word for it that this will take a while...

 

Gives me the NetworkSolutions page now...

...someone needs to pay their bills..