| |||||||
| Announcements Place for sffchronicles announcements, updates, and info on this website only. |
| Welcome to the Science Fiction Fantasy Chronicles forums | |
| Welcome to the chronicles network, the UK's largest - and friendliest - science fiction and fantasy forums!
If you love to read or watch science fiction and fantasy, you've come to the right place to be among like-minded people. And we count published authors, editors, and agents among our members, so have an especially strong community of aspiring writers. To post or reply to a topic you'll need to register - but don't worry, it's free and we don't pass on any of your details to anyone else. | |
![]() |
| | LinkBack | Thread Tools | Rate Thread |
| | #1 (permalink) |
| Brian G. Turner | DNS issues Terribly sorry for chronicles being down for a few hours this morning - one of the server techs needed to update the site's DNS - ie, the server's internet address - early this morning, but unfortunately was compiled on a secondary IP the server uses, taking down every single website on the server. Anyway, got it fixed now and hopefully should not be any further problems with this. |
| | |
| | #9 (permalink) |
| Wherever I Am, I'm There | Re: DNS issues I was concerned it might be my fault - I must have pulled on the server a lot yesterday - but I noticed a few of your other Britecorp websites were also down. I also hoped it hadn't crashed and gone down without a back-up. I would have wasted all my time. Glad everything is okay. |
| | |
| | #10 (permalink) |
| Knivesout no more | Re: DNS issues The Britecorp site itself was still up, so for a while I thought it was the underlying forum software (I've been seeing odd things happening at another forum run on the same platform). Fortunately it was just good old human nature. Chron always stays up is a good motto, considering some some of us never seem to sleep! |
| | |
| | #11 (permalink) |
| Brian G. Turner | Re: DNS issues It's okay Dave, no need to panic - the DNS issue took down every single website on the server - it was just because when we moved to this new server, we were moved over to a newer server a week later by the same hosting company. However, the DNS records were still all set up for the old server, so when DNS was updated on Friday night, it reverted to the new addresses, which had not been set up properly - hence why everything went screwy until this was all corrected. A big headache, but only a temporary pain. |
| | |
![]() |
| Thread Tools | |
| Rate This Thread | |
| |