Posts by kess

@Nuxwin Yes i know, you are right.
In fact generally you change TTL at least 2 weeks before the beginning of the server move, to the lowest accepted value.

But as I can understand @Dylan is a little bit late now, and he is going to have problems for sure.
What I implemented, simply resolves the queries done against the old DNS, with the new IP addresses. This has nothing to do with "propagation speed up". It's just a really dirty workaround in order resolve some parts of the problem.

The rest, is cached somewhere in multiple parts of the internet, where you have no control... So... Just wait...

On your old server run the following:

Where:
- 192.168.1.1 is your primary OLD IP Address
- 192.168.2.1 is your secondary OLD IP Address
- 172.16.16.1 is your primary NEW IP Address
- 172.16.17.1 is your secondary NEW IP Address

So, all the DNS queries performed against your OLD server, will receive the new IP addresses as answers.

Hope it helps,
bye Kess.

All these settings are relative to each domain independently from the others hosted on the same physical machine.
If you want to have these settings for all your domains, you must apply these settings to each single domain...

Create the following DNS Resource Records:

In order to create your own customized SPF record, try this one: http://www.spfwizard.net/
After doing that, consider also using DKIM on your domain. This Plugin

is your friend

With OpenDKIM consider also creating a DMARC DNS Resource Record, something like the following:

In order to create your won customized DMARC record, try this one: https://www.unlocktheinbox.com/dmarcwizard/
Bye Kess

Upgrade to Jessie. You'll find a lot of guides in order to do it.
Then reinstall i-MSCP

You need to use a listener in order to achieve that. For your particular problem, use that one:
https://github.com/i-MSCP/imsc…p_confoptions_override.pl

You're welcome

Undo everything you've tried for sqlite and then execute:

Hope it helps

For version 1.3.16, but I bet something similar on 1.4.1:

File /etc/php5/mods-available/ioncube_loader.ini

Then:

Test with:

I use php-fpm and I never lose my ioncube configuration even during i-MSCP upgrade.
When I create a new domain for a new customer he receives ioncube exactly like all the Others