Suggestion of FQDN for panel during installation

    This issue was seen also in previous versions:


    Dedicated server with installed OS from a template (here: debian jessie). As a parameter for the installation I could enter my own hostname (mysub01.mytop.tl). The server got also its own hostname (theirsub123.ispname.tl) which remains as an alias.


    When it comes to the suggestion for the panel-FQDN the default is


    panel.mytop.tl but should be panel.mysub01.mytop.tl?



    mysub01.mytop.tl
    mysub02.mytop.tl
    mysub03.mytop.tl
    ...
    all have their different IPs each. Any further subdomain (e.g. vu2005.mysub01.mytop.tl) is covered through wildcards.
    mytop.tl itself is unused. With the current behaviour all machines would get the same panel-FQDN.


    Not severe as one can change this value.

    Currently not using i-MSCP.

    Edited 3 times, last by sutorinfo ().

    @sutorinfo


    You're confusing server hostname which by default is filled with current server hostname <server>.<yourdomain.tld> (e.g: result of hostname -f) and the panel hostname which by default is set to panel.<yourdomain.tld>. We are considering the domain here (server hostname - one label) and then, we add the panel label (which is a subzone of yourdomain.tld). Anyway, you can always setup other values than default.



    i-MSCP installer ask you for the server hostname and the panel hostname.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    Thank you for your explanation. This is, how I understood this. My post was a bit unstructured. The case above will only be a problem when setting up multiple machines:



    Machine (loc) One (in FR) Two (in DE)
    IP (example) 17.108.9.22 102.47.11.05
    Servername as given by Service Provider (remains as alias) vs001.provider.net ma175.isp.com
    Servername FQ as given by Admin (myself) net1.server.org net2.server.org
    Suggested panel name bi i-MSCP panel.server.org panel.server.org
    Wanted panel name panel.net1.server.org panel.net2.server.org
    Annotations server.org itself may be located on a third machine.




    net1.panel.server.org will work too.



    There are two independent installation processes resulting in doubled domain names. I think, this will have some effect on the "M" in MSCP. Could be a feature, too, if from panel.server.org I could administer all machines where any of them containes all informations. Could serve for failover systems. Could work, if panel.server.org could get its own IP, but most Providers here offer only 1 (v4) per machine.


    In the installation process the first machine will act in the known way. When it comes to the second machine, the existing first one will be detected and its up to a subroutine to establish the communication chain (e. g. submitting all database entries to machine one, especially its own IP). But that belongs to your started discussion for i-MSCP v2.0.


    As you told above, we are able to edit this name (to wanted panel name) and this solution works for me. Only wanted to mention this usecase. Thanks very much again for your explanation.

    Currently not using i-MSCP.

    If you have done all preinstallation steps correctly, normally suggestion should be "Wanted panel name" instead of "Suggested panel name bi i-MSCP". I hope you've added the FQDN (net1.server.org|net2.server.org) in the hostname:

    Shell-Script
    1. echo 'net1.server.org' > /etc/hostname
    2. hostname -F /etc/hostname