Hello,
could I configure a secondary DNS after my I-Mscp is running ?
What config I will need change it and restart ?
Thank you.-
Martin
Hello,
could I configure a secondary DNS after my I-Mscp is running ?
What config I will need change it and restart ?
Thank you.-
Martin
Display More
Hello ;
if you are using last git master:
or
Thanks you for using i-MSCP.
Yes I'm using github master version.
I did, like root user :
I followed the instructions on the screen, but after "yes" at the question "Do you want add secondary DNS ?" show up one screen with the text "Please enter IP addess(es) for master DNS server(s), each separated by space" but MASTER or SLAVE IP ???
after made it with secondary IP's or mater IP on the server config nothing changed, here my bind config file :
Re ;
I'll try now and fix if needed.
Thanks you for using i-MSCP
Re ;
I'll try now and fix if needed.
Thanks you for using i-MSCP
Edit: Fixed in https://github.com/i-MSCP/imsc…b07c2000ae91cfccdb681ce4e
Just do a pull and rerun the installer as follow:
Thanks you for using i-MSCP
Display MoreEdit: Fixed in https://github.com/i-MSCP/imsc…b07c2000ae91cfccdb681ce4e
Just do a pull and rerun the installer as follow:
Thanks you for using i-MSCP
Nuxwin thank you a lot for the fix ! Works perfect !!!
I have a doubt, I was watching the config files and saw this config on the ns1.admin.vm0.domain.com.db on /etc/imscp/bind/working
This lines
should not be this way :
dns1.stabletransit.com and dns1.stabletransit.com are the secondary servers what I'm trying to use. Because ns2.admin.vm0.domain.com. and ns3.admin.vm0.domain.com. do not exist .
And how I will need to delegate the domain on TLD ?
ns1.admin.vm0.domain.com
ns2.admin.vm0.domain.com
ns3.admin.vm0.domain.com
or
ns1.admin.vm0.domain.com
dns1.stabletransit.com
dns2.stabletransit.com
This is only a theoretical question, I'm not a expert on DNS
Re ;
By default, i-MSCP make assumption that you have one glue record for each server/domain, eg;
ns1.domain.tld ---> server ip
ns2.domain.tld ---> server ip
ns3.domain.tld ---> server ip
In your case, you seem to already have two slave DNS servers with the following glue records:
dns1.stabletransit.com ---> server ip
dns2.stabletransit.com ---> server ip
If you want reuse the same names for your secondary slave DNS servers, you must modify the i-MSCP templates located under /etc/imscp/bind/parts and rerun the i-MSCP setup script (/var/www/imscp/engine/setup/imscp-setup).
Don't forget that if you rerun the imscp-autoinstall script, the template will be overwritten. That for this reason that I tells you to run the imscp-setup script instead of the imscp-autoinstall script.
i-MSCP DNS management layer will be review as soon as possible since many bugs were found into it. For instance, during i-MSCP setup, you are asked for the domain from which the panel must be accessible and then a dedicated DNS zone (such as admin.domain.tld) is created. This way to process is wrong because if later you create the domain domain.tld from the panel (as customer account), an other zone domain.tld will be created. This will cause side effects such as unreachable domain (randomly on domain.tld or panel.domain.tld), depending of how the DNS of your FAI is working (DNS cache issues). This problem can be solved in two ways: Making panel.domain.tld a pseudo subdomain by adding it as simple A record in the domain.tld zone or by delegating it.
Thanks you for using i-MSCP
To read
- http://faq.domainmonster.com/dns/glue_record/
- http://www.zytrax.com/books/dns/ch9/subdomain.html
- http://www.zytrax.com/books/dns/ch9/delegate.html
- http://docstore.mik.ua/orelly/…ing_2ndEd/dns/ch09_04.htm
Display More
Re ;
By default, i-MSCP make assumption that you have one glue record for each server/domain, eg;
ns1.domain.tld ---> server ip
ns2.domain.tld ---> server ip
ns3.domain.tld ---> server ip
In your case, you seem to already have two slave DNS servers with the following glue records:
dns1.stabletransit.com ---> server ip
dns2.stabletransit.com ---> server ip
If you want reuse the same names for your secondary slave DNS servers, you must modify the i-MSCP templates located under /etc/imscp/bind/parts and rerun the i-MSCP setup script (/var/www/imscp/engine/setup/imscp-setup).
Don't forget that if you rerun the imscp-autoinstall script, the template will be overwritten. That for this reason that I tells you to run the imscp-setup script instead of the imscp-autoinstall script.
i-MSCP DNS management layer will be review as soon as possible since many bugs were found into it. For instance, during i-MSCP setup, you are asked for the domain from which the panel must be accessible and then a dedicated DNS zone (such as admin.domain.tld) is created. This way to process is wrong because if later you create the domain domain.tld from the panel (as customer account), an other zone domain.tld will be created. This will cause side effects such as unreachable domain (randomly on domain.tld or panel.domain.tld), depending of how the DNS of your FAI is working (DNS cache issues). This problem can be solved in two ways: Making panel.domain.tld a pseudo subdomain by adding it as simple A record in the domain.tld zone or by delegating it.
Thanks you for using i-MSCP
To read
- http://faq.domainmonster.com/dns/glue_record/
- http://www.zytrax.com/books/dns/ch9/subdomain.html
- http://www.zytrax.com/books/dns/ch9/delegate.html
- http://docstore.mik.ua/orelly/…ing_2ndEd/dns/ch09_04.htm
Thank you for your answer !
Martin
Hi,
do i have to run the installer on server that should become the secondary ns, or the i-mscp mainserver ?
Best wishes
Niels
Hello ;
Regarding the subject of this thread, you must run the installer on the i-MSCP main server.
Thank you for using i-MSCP