Beiträge von ñull

    Sometimes the WYSIWYG editor would work in this forum. I tried to manipulate my user settings, but it did not help to reactivate it. At the moment it is all very minimalistic and I cannot even make my text more readable with paragraphs, because my line breaks are ignored and all text is displayed joined together. Please could you improve the settings to allow at least some simple formatting?

    The cause is explained

    . The faulty subscription is listed but is not usable for domain creation. Still the same there is no way to create "internal" (DNS) domains. With a correct subscription (created with a predefined hosting plan) the domain will be created as external (DNS) by default and there is no documented parameter for HostingDomainAdd to change the default.

    HostingSubscriptionAdd will in certain circumstances create a subscription in an undefined state with unpredictable results. When you create an individual subscription its name will appear in the front-end but it cannot be used nor selected when adding a new domain. This must be the cause why I could not use HostingDomainAdd to add a domain (see for more information

    and

    ). The work around at the moment is to work with predefined hosting plans. These can be prepared in the web front-end with all the parameters and will create a working subscription.

    I discovered that xdebug in "Step over" mode will not show the Soap errors but with Breakpoints I can see them. The subscriptionname used and returned with HostingSubscriptionAdd is the same as I use in HostingDomainAdd. When I check in the web interface I can see a subscription is created with the same name. Still HostingDomainAdd returns the error message "Invalid subscription (no record found)". This bug effectively blocks my migration efforts.

    I'm only guessing here. I was able to add a subscription but then when I log in as client, then it only displays the subdomain limit:


    Code
    Contract      Domains   Subdomains
    <cntr-name>   0         0 (unlimited)



    Then when I try HostingDomainAdd with the soap api, it returns without error, but it stops execution of the script and no domain is added. Apparently by default an internal domain is supposed to be added, but since the limit is not clearly defined, it apparently fails.


    Also, when this is by default an internal domain that is added, then there should be a parameter to set the DNS template.


    I feel like to report this as bug now: https://www.liveconfig.com/de/…t-working?p=6244#post6244

    What happens when afterwards I put a value?


    I pretend to use this to quickly migrate my accounts from the other server and then afterwards account after account adjust the quotas manually. I try to avoid complicated algorithms in my script to work around quota overselling in the previous control panel.

    Well I am afraid we were both mislead. I found out it had to do with the host name of the server, which by force is the host name of the primary DNS in a new template and by force is the hostname of the MX record in a new zone. When in test fase this hostname was just set to something that does not resolve the an IP address. Consequently bind will consider the domain zone invalid and responds to dig queries accordingly.


    When I set in the /etc/hosts the address hostname to the IP address of the server, then suddenly bind considers the zone valid and dig responses correctly.


    Sorry for wasting your time this way, but at least I learned something.

    Above the mailbox quota value of 2047GB, unexpected values are stored, even negative. I know it is a crazy high value, but validation should take care of this correctly, warning the user that a maximum limit has been passed. It should not store incorrect values.


    This happened when I set the hosting plan quota to unlimited. See also the related question about the meaning of "unbegrenzt"

    I please need an explanation of what "unbegrenzt" means in the context of the parameters mailquota and webspace of the command HostingSubscriptionAdd. I know what the German word means, but I don't know how LiveConfig handle this non-value. For instance, when I create an account with both unlimited webspace, how is that handled? What if both mailquota AND webspace are unlimited? What happens when there are more then one account that have unlimited webspace and/or mailquota?

    has no positive effect. I went to another server with ubuntu 12.04.3 LTS. Same problem. Now when I rewrite the zone file to this format it starts working:

    Backend is SQLite. I did the change in bind.lua, restarted and switched to external dns and back again. Same result:

    I tried something else I found in this thread:


    Code
    /usr/sbin/named-checkzone domain.com.db /var/lib/bind/domain.com.db
    /var/lib/bind/domain.com.db:11: ignoring out-of-zone data (domain.com)
    /var/lib/bind/domain.com.db:19: ignoring out-of-zone data (dev.domain.com)
    /var/lib/bind/domain.com.db:20: ignoring out-of-zone data (www.domain.com)
    zone domain.com.db/IN: has 0 SOA records
    zone domain.com.db/IN: has no NS records
    zone domain.com.db/IN: not loaded due to errors.

    When 10.0.0.164 is the ip address of the bind server and domain.com is configured in LC with "Own DNS server" with a valid DNS template, then I correctly see in /etc/bind/zones.liveconfig:

    Code
    zone "domain.com" {
    	type master;
    	file "/var/lib/bind/domain.com.db";
    	update-policy { grant LiveConfig. subdomain domain.com. ANY; };
    };


    ... and /var/lib/bind/domain.com.db:


    ... but still the dig command will return:



    Why is it failing? What is missing?

    Presently the number of aliases (according to the SOAP reference documentation) is hard-coded and limited to 10. With the present available versions, is it be possible to override this maximum, in the configuration file for instance? Ideally I would think this limit should be set in the Hosting plan. In fact you have already the maximum number of addresses and mailboxes. Wouldn't these two settings not be sufficient to limit excessive use of addresses? Or was there any technical reason why this extra limit was added and hard-coded?