Posts by theemstra

  • OOBE -- Out Of the Box Experience

    What's I would love to be implemented in I-MSCP is an Out of the Box Experience.
    Let me elaborate.


    What I would like is a feature that would allow my customers to order a domein/hosting package on my website (external) and while they can't see it, there's a process that creates a hosting package with domain automatically

  • Mail forwarding doesn't work?

    Maybe this is related, not sure.
    If there's no accounts set on a domain and you create a catchall, it will not work.
    You need at least one account on the domain for the catchall to work.


    Linux Distro
    Debian
    PHP Version5.4.4-14
    i-MSCP Version1.1.14

  • v1.1.0.RC4.3 - Managed to confuse the database - setup script now failing

    Some more information here:


    On the main server, this is correct:

    Code
    1. ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> domain.tld;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2248;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;domain.tld. IN A;; ANSWER SECTION:domain.tld. 10800 IN A {IPADDR};; Query time: 0 msec;; SERVER: 127.0.0.1#53(127.0.0.1);; WHEN: Tue Jul 29 09:15:07 2014;; MSG SIZE rcvd: 50


    Now on the slave, same domain, when requested remotely:

    Code
    1. dig domain.tld @slaveserver; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> domain.tld @slaveserver;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 20136;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0;; WARNING: recursion requested but not available;; QUESTION SECTION:;domain.tld. IN A;; Query time: 7 msec;; SERVER: ipv6-addr:53;; WHEN: Tue Jul 29 09:16:27 2014;; MSG SIZE rcvd: 34


    On slave server, now local:


    This shows that the slave server does actually see the remote zone, but will not answer authoritive when asked from remote servers.

  • DNS entry '@' makes zone invalid

    It is not possible to add a custom dns CNAME entry with content @, which points back to the zone name (domain.tld or subdomain.domain.tld).
    When a user tries this the zone becomes invalid and manual removal is required.


    Reproduce:
    Login as a user.
    Create custom dns record
    choose CNAME, give the record a name and fill in @ for content.
    Wait a few seconds and check out the domain status.

  • v1.1.0.RC4.3 - Managed to confuse the database - setup script now failing

    Hi Nuxwin,


    Thanks again for taking the time to respond.
    I've found and fixed the problem.
    I had changed the dns template, but made a type (one double . with CNAME), after removing the domain name failed php-fpm config wasn't deleted properly.
    After searching good and well it started working again.


    I curreltly have two NS'ses installed, both with imscp.
    Customers could use the main server, the second one is used for backups and ns2.


    When I try testing the second nameserver (set up via the setup script) it just gives me "not authoritative" answers.
    After checking, it seems that imscp does not set up slave records in named.config.local, is that right or did I do something wrong?

  • v1.1.0.RC4.3 - Managed to confuse the database - setup script now failing

    Quote from Nuxwin

    @theemstra


    And so?


    Do you are asking us how to solve your own mistakes ? If you start to customize i-MSCP, this mean that you know what you're doing. Here I see one possible issue: Orphan entry. You must now check the database to be sure that all data which belong to the domain you want to remove are deleted.


    Hi Nuxwin,


    Thanks for taking the time to answer.
    Could you tell me if there's any development in using multiple nameservers and also providing the bind DNS zones with multiple NS entries?


    I'll have a look at the deletion process, but that's only part of the problem.
    Also when registering a new domain in the system the error (below) appears in the domain status unknown.

    Code
    1. Servers::named::bind::_addDmnDb: Unable to install lala.com.db


    I can't be the only one here trying to configure a second (maybe a third) NS for a domain.


    Best regards

  • v1.1.0.RC4.3 - Managed to confuse the database - setup script now failing

    I know that bumping an old topic isn't the way we'd like this to go down, but in the most recent version of i-MSCP (1.1.13), I am still having this issue.
    After adding a domain to i-MSCP, I get an unknown error (domain status) and when I check the details it gives me this error for example:

    Code
    1. Servers::named::bind::_addDmnDb: Unable to install lala.com.db


    I was not able to find the issue, even with the DEBUG mode set to 1.
    The request manager pl script didn't give any errors either.
    The cp seems to be able to remove the domain, but when I try to re-add it, it gives me:

    Code
    1. Domain lala.com is unavailable.


    I have (like TS) altered the template file with an extra nameserver, guess that is what is causing all of this.


    To reproduce:
    Edit the db.tpl file in /etc/imscp/bind/parts and add a domain, now wait a few seconds and click details.