Posts by ctct

    Hi guys


    After upgrading to the latest i-MSCP Version my External Mail Servers where not activated, so I activated them but I get the following Message when sending Emails to the external Domain:
    Status: 5.4.6
    Diagnostic-Code: X-Postfix; mail for myexternalcomain.de loops back to myself


    So I tried to add a csutom dns record thinking this might solve the issue. Then I noticed that when adding a record with an external Host name, the Domain "mydomain.com" gets appended to the end of the Host:
    Should be: customer-de.mail.protection.outlook.com.
    Turns to: customer-de.mail.protection.outlook.com.mydomain.com.


    Is this a bug? I thought it should only append the domain if its not FQDN.


    Cheers
    Ron

    Hello guys


    Is there a way I can override the default www and @ (non-www) DNS records to point to an external server? We have a scenario where a customer wants to host the email on our server but point the www and @ to an external webshop.


    i-Mscp 1.2.2
    Debian Squeeze


    Thanks


    Regards
    Ron

    Hello theemstra


    I finaly got it working now. I reinstalled and now seems to work.


    However a strange thing happens:
    The previous control panel page returns a domain alias of a customer.
    It used to be cp.lion.tdl.com now it is cp.lion.dtl.com:3726.
    When I navigate to the cp.lion.tdl.com it show the page.


    Thanks.
    Regards
    Ron


    Where did you host your dns? sounds not really related to imscp ;)


    Thanks for the reply. I have pointed my Domain to the i-mscp Server without a external host, so its on the i-mscp Server. It all works fine, but the DNSstuff.com brings up an error saying the above. So I guess I need to get i-mscp to respond with ns1.myserver.com and not ns1.customerdomain.com. How? Or is this an intended result and I should be using ns1.customerdomain.com?


    Thanks.
    Ron

    Hello


    I have my Domains pointing to my Server ns1.myserver.com and ns2.myserver.com but the Server responds with the ns1.domain.com and ns2.domain.com of the virtual Domain.


    I get this from DNSStuff:

    Quote

    Parent zone does not provide glue for nameservers, which will cause delays in resolving your domain name. The following nameserver addresses were not provided by the parent 'glue' and had to be looked up individually. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.


    and this:

    Quote

    Stealth Nameserver
    One or more stealth nameservers discovered. This means that one or more nameservers are not listed at both the parent and authoritative nameservers. This can be confusing and can cause delays or other hard to diagnose inconsistencies. The stealth nameservers discovered are:


    How can I solve this issue and get my Server to pass on the real NS info rather than the ns1.customerdomain.com and ns2.customerdomain.com?


    Thanks for your help.
    KR
    Ron