No, it's not on Keith's servers.
Seems to have got a bit better now, fingers crossed they've fixed it.
If I have to move it, there might be a bit of down time to get everything working.
No, it's not on Keith's servers.
Seems to have got a bit better now, fingers crossed they've fixed it.
If I have to move it, there might be a bit of down time to get everything working.
No it hasnt, Slopp.
Worse than ever here.
T%his is my fourth attempt to post something...-)
If they can't fix it, I'll be moving to a dedicated server.
It's a fair bit of effort so it's not going to happen quickly.
Your patience is appreciated until I can sort it out.
Sorry Guys
I paid a pound, yes, a WHOLE DAMNED POUND for this service!
Oh, I see...
It'll be worth waiting for, Sloop.
And worth paying more than a pound for...
I'm working on it.
I know...-)
I have been doing som checking and noticed that the DNS servers for the domain were not setup correctly.
I have added the 3rd name server, but it will take a while for the DNS records to update.
I believe the problem to be caused by a record pointing to ns3, when ns3 was not listed as a name server for the domain.
For info:
CheckDNS.NET is verifying if NS are alive
NS list mismatch: registration authority reports that domain is hosted on the following servers: 'ns2.livedns.co.uk; ns1.livedns.co.uk', but DNS server ns1.livedns.co.uk reports domain to be hosted on 'ns1.livedns.co.uk; ns2.livedns.co.uk; ns3.livedns.co.uk'. Please make sure that you configure the same DNS servers in registrar database and on your DNS
I haven't paid a pound yet but it's not for want of trying.
I'm quite will to pay more than a pound though too.
And yes it does seem that it's just as bad if not worse in patches.
Bookmarks