On the future of the forums

[JohnE]

I'm sure I'm not just speaking for myself in thanking Sigma for making the transition as smooth as possible.  Many <3s to Sigma.

Indeed. Thank you Sigma.

[Valerius]

I just tried typing fqa.digibase.ca into the address bar in my browser and nothing came up. Didn't get rediredted to FSTDT either. Tried it on 3 other browsers as well and got the same result. Is the server down, or is my computer just being weird or something?

[The Right Honourable Mlle Antéchrist]

It's working for me.

[Nightangel8212]

I just tried typing fqa.digibase.ca into the address bar in my browser and nothing came up. Didn't get rediredted to FSTDT either. Tried it on 3 other browsers as well and got the same result. Is the server down, or is my computer just being weird or something?

I can't get it to work for me either... what's going on? I tried on both my servers and I can't get anything.

[Lithp]

I got it to work too, but I was signed out in that window, for some odd reason.

[Nightangel8212]

I got a hold of Kradorex in the fstdt IRC and he fixed an issue, so it's working for me now.

[RavynousHunter]

I got it to work too, but I was signed out in that window, for some odd reason.

Likely because its, technically, a different site and therefore has a different set of cookies; the two don't mingle with one another even though both URLs are pointing to the same location.

[Canadian Mojo]

The only thing I dislike about not losing everything is that I can't make a new "Thread Killer?" containing the proper intro post. I feel like I've forever disappointed Sigma in that regard.

Make a new thread killer anyways. We could always use a second one with our propensity to break off into tangents.

I'm so tempted.

C'mon... you know you want to.... do it, gurllllll

What would be cool is if we start a new one, get the old one locked, collect the Thread Killers of previous board incarnations, and put the whole shooting match in it's own area on the new board. Make it the Thread killer through the ages.

[Sleepy]

That is the best idea I've ever heard for anything ever.

[Valerius]

I got a hold of Kradorex in the fstdt IRC and he fixed an issue, so it's working for me now.

Works for me too, now. Maybe it was a regional issue? I thought I read somewhere that you live in the same city I do. I don't know if that would affect it though. But whatever, it works now so that's good.

[Kradorex Xeron]

I got a hold of Kradorex in the fstdt IRC and he fixed an issue, so it's working for me now.

Works for me too, now. Maybe it was a regional issue? I thought I read somewhere that you live in the same city I do. I don't know if that would affect it though. But whatever, it works now so that's good.

It was an issue with our contracted DNS secondary servers. Our central server (ns.digibase.ca) was updated, but our secondaries (externally hosted, ns2.digibase.ca and ns3.digibase.ca) that are supposed to synchronize records failed to do so.

DNS is essentially the phonebook of the Internet, changes names, (e.g. fqa.digibase.ca) into IP addresses (e.g. 72.38.129.202) so computers can connect using names, authoritative DNS servers hold records for a domain name and and respond for that domain. What happened here is some people were getting replies from our own in-house authoritative (Which had the record, they got access) while others were getting replies from our secondary authoritatives (Which did not have the record, which caused connection failed errors).

This has since been corrected as Nightangel brought the issue of the de-synchronization to my attention.

[anti-nonsense]

Thanks Sigma.

[Vypernight]

So is the new board up yet?  If so, what's the link?

[Valerius]

I got a hold of Kradorex in the fstdt IRC and he fixed an issue, so it's working for me now.

Works for me too, now. Maybe it was a regional issue? I thought I read somewhere that you live in the same city I do. I don't know if that would affect it though. But whatever, it works now so that's good.

It was an issue with our contracted DNS secondary servers. Our central server (ns.digibase.ca) was updated, but our secondaries (externally hosted, ns2.digibase.ca and ns3.digibase.ca) that are supposed to synchronize records failed to do so.

DNS is essentially the phonebook of the Internet, changes names, (e.g. fqa.digibase.ca) into IP addresses (e.g. 72.38.129.202) so computers can connect using names, authoritative DNS servers hold records for a domain name and and respond for that domain. What happened here is some people were getting replies from our own in-house authoritative (Which had the record, they got access) while others were getting replies from our secondary authoritatives (Which did not have the record, which caused connection failed errors).

This has since been corrected as Nightangel brought the issue of the de-synchronization to my attention.

Makes sense. I know absolutely nothing about stuff like this, so thanks for the explanation.

[Her3tiK]

Well this looks new. This the layout of our new digs?