Posts by Nuxwin

  • Utiliser Php-5.6 et 7.2 sur mon serveur

    Quote from FloRet88

    If you would like to do it manually - you should be experienced enough how to do such things as system administrator.

    The plugin will support you to do it easily!

    I don´t think, that in future I-MSCP Versions the functionality of the Plugin will included in the core!

    Best regards

    Those french people... They always want all for free. That explain why I don't work with them ;) Sure, I'm also one of them but only on the paper, I'm german/swiss in heart. :P

  • Utiliser Php-5.6 et 7.2 sur mon serveur

    Quote from denzwell

    Bonjour,


    Merci pour votre réponse. c'est un plugin payant pour 32 €uros.
    Je vais attendre la prochaine version de imscp ou tester un autre web panel.


    Mais est ce compliqué de le mettre en place manuellement ? Si vous avez un lien un tuto, je suis preneur


    Merci encore

    Les Français et leur radinerie mondialement connue 8o


    Les prochaines versions d'i-MSCP ne vous permettrons pas d'avantage de fournir différentes versions de PHP à vos clients sans cette extension. Nous fournissons une solution gratuite pour la gestion des hébergements Web partagés mais nous devons aussi gagner notre vie.


    Les extensions et le support que nous fournissons sont notre seule source de revenus. Libre à vous d'implémenter votre propre solution, ou d'aller voir ailleurs si l'herbe est plus verte mais ne nous demandez pas de vous fournir une solution clé en main gratuite alors même que nous fournissons déjà une solution payante. Bref, je penses que vous m'avez compris.

  • Strange zone expired in BIND problem between i-MSCP master / slave servers.

    Quote from jackstone

    One question remains, do I have to edit named.conf.local every time I add a new domain for a client adding { localhost ; slaves; } or is there some setting in i-MSCP that can do that automatically ?!

    Good evening,


    You can modify default templates which are located into the /etc/imscp/bind/parts directory:

    But the problem is that your changes would be overridden on next i-MSCP update. Thus, the right way to do is to edit the SECONDARY_DNS configuration parameter from the /etc/imscp/bind/bind.data configuration file. Value of that parameter should be the list of your slave DNS servers. For instance:

    Code
    1. # List of IP addresses for slave server(s)
    2. # Only relevant in master mode
    3. SECONDARY_DNS = 192.168.1.100,192.168.2.100

    where

    1. 192.168.1.100 would be the IP address of your NS1 slave DNS server (public)
    2. 192.168.2.100 would be the IP address of your NS2 slave DNS server (public)

    Please don't put ACL there. This wouldn't work as the backend expect list of valid IP addresses. We could maybe support ACL in later release. Feel free to open a feature request on our bug tracker if needed.


    Note that there is no need to add the localhost entry. The backend will add it automatically. The related code in the latest release look as follows:


    ./engine/PerlLib/Servers/named/bind.pm (line 894):


    See https://github.com/i-MSCP/imsc…ervers/named/bind.pm#L894 for more details.

  • Strange zone expired in BIND problem between i-MSCP master / slave servers.

    jackstone


    Re,


    The slave servers refresh their zones automatically by contacting the master DNS server . This is dicted by the SOA refresh value which for the i-MSCP DNS zones is set to 3 hours (default value).


    So, a slave DNS server will contact the i-MSCP master DNS server every 3 hours to check whether or not the SOA serial value (on a per zone basis) as been updated and if so, will request a new copy of the zone. However, if the slave DNS server cannot get a new copy of the zone when the SOA serial value has changed, it will still considere old zone data as valid till expiry time, as dicted by the SOA expiry value. That value is set to 2 weeks for the i-MSCP DNS zones (default value). If after two weeks, the slave DNS server still fail to get a new copy of the zone, it will no longer answer to DNS queries.


    Here, you need to make sure that:

    1. Slave DNS servers can contact the i-MSCP master DNS server to check whether or not the SOA serial value of a specific zone has been updated or not
    2. Slave DNS servers can request a new copy of the zone.

    You need of course also make sure that the slave DNS servers will get notified by the i-MSCP master DNS server when a zone is being updated. This mean that slave DNS servers must accept notifications from i-MSCP master DNS servers as well.


    Please check your configuration because it seem you miss-configured some parts. For instance, the directive allow-notify only apply to slave DNS zones. Thus, that directive shouldn't be added into the i-MSCP master DNS configuration file.


    Another thing is about the allow-transfer directive which, if added in the zone declaration, will take precedence over the global one. Thus, the following declaration in your i-MSCP master DNS server named.conf.local configuration file:

    Code
    1. zone "blabla.com" {
    2. type master;
    3. masterfile-format raw;
    4. file "imscp/master/blabla.com.db";
    5. allow-transfer { localhost; };
    6. notify yes;
    7. };

    should becomes:

    Code
    1. zone "blabla.com" {
    2. type master;
    3. masterfile-format raw;
    4. file "imscp/master/blabla.com.db";
    5. allow-transfer { localhost; slaves; };
    6. notify yes;
    7. };

    and of course, you should add the corresponding ACL in the i-MSCP master DNS named.conf.options configuration file such as:


    Code
    1. acl "slaves" {
    2. ............; // NS1 (slave)
    3. ............; // NS2 (slave)
    4. };