Forum struggling to load

[Polchraine]

Over the past few days access has been like wading through treacle along with numerous failures. This morning it was near impossible to access pages and watching the host server, I could see it going up and down like a *'s **s on a Saturday night.

But now, it seems lightning fast ...

What did Christel threaten them with?

[ovenpaa]

Not sure what she said to them but she just pinged me to say she had just received the invoice and paid it and an upgrade was two hours away and would be seamless... Yeah right!

I feel an interesting 24 hours coming on and the database has been backed up just in case.... :lol:

Cross you fingers FB'ers

[Christel]

I bribed them. :lol:

Hopefully the morning spent on live chat and being sent from one department to another and paying the additional invoice (that it has taken them since last week to send me!) has paid off.

At some point today they will move us to a different server. I hope it goes ok.

Cross your fingers it is all running smoothly from now on. Of course with the exception of when they do maintenance and....and....

:G

[Christel]

Yes, thank you for the back up, good idea.

[Polchraine]

Moving to another server will probably mean a change of IP address ...

That could result in an hour of downtime before the new address is propagated to key DNS servers and up to 24 hours for it to go world wide.

[Christel]

I did ask about exactly that but I was told to wait for support to get back to me. So now I am waiting...

[rox]

Moving to another server will probably mean a change of IP address ...

That could result in an hour of downtime before the new address is propagated to key DNS servers and up to 24 hours for it to go world wide.

Since you manage your own DNS you should set the TTL to the minimum possibe value sufficiently in advance of any expected change, then when you update the 'A' record it should propagate as quickly as possible. Keep it low for a while until things are stable in case another change or revert is required.

The TTL for the relevant record is currently set to 14400s (4h). If possible reduce this to 5 mins or less. Wait 4 hours for that to propagate then lock the site, copy the database and make the DNS change.

..