can't view the board at home

[bigsur78]

"Oops! Google Chrome could not find http://www.offsetguitars.com" onclick="window.open(this.href);return false;
Suggestions:
Access a cached copy of www. offsetguitars. com
Try reloading the page
Search on Google:"

Still no luck after clearing the cache on Chrome, Explorer and Firefox on two different laptops. For whatever reason, OSG is not liking my IP, both at work and home. For now I am still "undercover" and accessing it fine, but just to let you know the issue remains...

[parry]

the offset gods have deemed you unworthy after 5pm.

I'm NEVER worthy... guess it's just catching up with me...

[Jay]

So I tried clearing out a couple things (and failed fixing a couple more) so I guess just give it another go?

I'll see if I can give another option a go this evening when I'm home from work.

[bigsur78]

that's alright i kinda dig the outlaw thing
thanks for your efforts Jay.

[parry]

Damned Canadians...
always messing up everything

Thanks, Jay!

[Jay]

I got some info from our host. Apparently we had a nameserver change and one of the nameserver addresses never got updated by the domain host so anyone hitting that particular server to resolve the IP would have been unable to get it. It should work itself out now within the next 24 hours.

[Stratelejazzuar]

hey, i've bee at my mom's place for a few days and since last week (wed or fri) i couldn't access OSG here, but fine at my own place.

tribi9 was having issues last night, too, and we couldn't figure it out. my mom suggested it was the ISP, Rogers, and she actually called and started talking to whomever... i wsn't around, but i think she tried the DOS mode thing and maybe a couple other quick fix troubleshoots. the next step would've been hard resets of modem and trying to plug line straight into the comp instead of a router hookup. we didn't try that stuff, cuz i don't have THAT big of a problem to OSG yet, lol.

i tried a few times today, and still got the same can't connect error page, but now it's good again!

[bigsur78]

WORKING! Good job Jay.
Funny, it definitely seems to have been a north-of-the-border problem...
I'm on Rogers as well.

[crazyzeke]

I got some info from our host. Apparently we had a nameserver change and one of the nameserver addresses never got updated by the domain host so anyone hitting that particular server to resolve the IP would have been unable to get it. It should work itself out now within the next 24 hours.

I saw that last week, I assumed the site had gone down though it seemed like a longer time than average, although it was back up within cheesecake.

[artie]

hmm... none of the things mentioned before worked.
however i CAN access it with ipshade.org

seems like the site doesn't like my IP address!! well at least i can go around that now. so thanks for mentioning ipshade.org!

[Jay]

hmm... none of the things mentioned before worked.
however i CAN access it with ipshade.org

seems like the site doesn't like my IP address!! well at least i can go around that now. so thanks for mentioning ipshade.org!

You shouldn't have to use that anymore. The reason you aren't able to access it is because the DNS server at your ISP has an incorrect name server address in its cache. There are two and one was entered incorrectly by our host when it moved. Like I mentioned above, that mistake was sorted out earlier today and once it propagates through the system (could take 24 hours) everything will likely be back to normal.

[parry]

Nice.
Everything works nice and smooth now.
Thanks again


(I'm on Rogers at home too, boys)