forum back up

[Chris333]

This whole forum outage is fishy. I suspect "virtual tom" is the culprit.

[ednadolski]

Someone has suggested that it's not an issue here at Railwire or a browser issue but the now outdated DNS information at some of the ISPs, and that's why it affects some but not others.

I'm pretty sure it had to be something like that.   I couldn't get it to work even after clearing my browser cache, all cookies, and rebooting.  Yet at the same time it was working from my computer at work.

Whatever cached info was out in the 'ether' seems to have expired or been evicted, since it's now working OK on both my systems.

Ed

[conrail98]

I'm pretty sure it had to be something like that.   I couldn't get it to work even after clearing my browser cache, all cookies, and rebooting.  Yet at the same time it was working from my computer at work.

It is definitely DNS issues. At home, I was fine. At work, I am not. The issue is that www.therailwire.net and therailwire.net are not resolving to the same IP address at work. I attempted nslookups on each at work and they came back with two different IP addresses. DNS refreshes will generally execute within 48 hours of any changes. We're now on Day 5 of this so that is why I believe it is not an issue with DNS per se, but perhaps a faulty nameserver at our host,

Phil

[Philip H]

Well I'm now back up on my Blackberry (!), at home on Safari, and at work on Firefox.

[Puddington]

Thanks to my new hero, Phil Duba, I'm back... he had me put a specific ip entry into the hosts file and that get me back in.....

Thanks Phil; you "da man"................

[Philip H]

Guys named "Phil" tend to be Da Man regardless of situation!

 

[Bremner]

sorry it took over 24 hours...some of my more $-generating forums (read: adult photo-oriented) I had to tend to first.

links, usernames and passwords are required

[Stourbridge Lion]

Rare poster here but I too can report that I have regained access to the site today so I think the access issue is nearly gone...

 

[tom mann]

Thanks to my new hero, Phil Duba, I'm back... he had me put a specific ip entry into the hosts file and that get me back in.....

Thanks Phil; you "da man"................

The problem is that this will break if my IP address changes in the future.

[tom mann]

We're now on Day 5 of this so that is why I believe it is not an issue with DNS per se, but perhaps a faulty nameserver at our host,

Phil

Again Phil:  I switched hosts Monday night (not day 5) so we should be in the clear after tonight.

[John]

The forum is hosted at IP

Non-authoritative answer:
Name:    therailwire.net
Address:  184.172.188.195

If you open a cmd prompt in windows and type nslookup therailwire.net and you get anything else - you are not pointing to the right place.

[conrail98]

The problem is that this will break if my IP address changes in the future.

Right which is why I told Mike I'll test it out on Friday without host entries on my work machine since that is where I was seeing the same issue everyone else had and see if we still need them or not. I'm aware it'll break if the IP changes but it's a two second fix with nslookup,

Phil

[conrail98]

The forum is hosted at IP

Non-authoritative answer:
Name:    therailwire.net
Address:  184.172.188.195

If you open a cmd prompt in windows and type nslookup therailwire.net and you get anything else - you are not pointing to the right place.

Which is what the issue was for most people, it was still pointing to the other address. Next time hosts have to switch, I suggest asking the new host or DNS record holder if the TTL can be lowered to less than 2 hours so we avoid the whole panic that sets in from people who may have it take the full 72 hours it can for DNS changes to reach them, particularly those that aren't as computer savvy as some here,

Phil

[John]

Which is what the issue was for most people, it was still pointing to the other address. Next time hosts have to switch, I suggest asking the new host or DNS record holder if the TTL can be lowered to less than 2 hours so we avoid the whole panic that sets in from people who may have it take the full 72 hours it can for DNS changes to reach them, particularly those that aren't as computer savvy as some here,

Phil

Phil ... I've done this a few times .. and in most cases, the DNS records update within 24 hours .. besides, it's a train forum, not a high availability e-commerce site like BBros ..

[Ian MacMillan]

  Bbros.


heheheheheheheheheheh bang