Sorry for my outdate solution.
I didn't find your post when I searched for "auto secondary dns server".
I only found the ispcp solution and I tried to modify that.
Your solution is better, thank you!
Sorry for my outdate solution.
I didn't find your post when I searched for "auto secondary dns server".
I only found the ispcp solution and I tried to modify that.
Your solution is better, thank you!
Hi,
is it possible to get this Guide also in english?? Thank you
Yes, of course. It's already done:
http://forum.i-mscp.net/Thread…ical-secondary-DNS-server
Original: http://noe.wikidot.com/automat…ndary-dns-for-ispcp-howto
It was revised for i-MSCP.
[size=x-large]1. on i-MSCP server (primary DNS)[/size]
[size=large]1.1. domain list query[/size]
Create the /var/www/imscp/gui/public/domainlist.php file with the following content:
Change the owner of the file:
To protect the domainlist.php create the /var/www/imscp/gui/public/.htaccess file with following content:
After that only the secondary DNS server can reach the file.
[size=large]1.2. BIND9 setup[/size]
Go to the directory of bind9 in order to create the communication key between the two bind9:
To speed up the generation type something on the keyboard!
After the key was created to view the key in base64 encoding form type the following command:
It will be neccessary later!
Append the following content to the /etc/bind/named.conf.options file (after the options {} content)
After that restart the BIND9:
[size=x-large]2. On the secondary DNS server[/size]
[size=large]2.1. BIND9 setup[/size]
Append the following content to the /etc/bind/named.conf.local file:
Append the following content to the /etc/bind/named.conf.options file (after the options {} content)
After that restart the BIND9:
Let's test to get the domain list from the primary server:
If we can see the DNS-zone definitions everything works well and we can set the automatic update by cron.
Create the /etc/cron.d/imscp_dns_update file with the following content:
So the DNS-zone definitions are automatically updated every 5 minutes from the primary server. If we do everything properly, we can see the <domain>.db files in the /var/cache/bind/ directory.
Finally hurray!
Eredeti: http://noe.wikidot.com/automat…ndary-dns-for-ispcp-howto
Átírtam, hogy i-MSCP-vel működjön.
[size=x-large]1. i-MSCP szerveren[/size]
[size=large]1.1. domain list előállítása[/size]
Hozzuk létre a /var/www/imscp/gui/public/domainlist.php fájlt az alábbi tartalommal:
Állítsuk be a tulajdonosát:
Védjük meg a fájlt a külvilágtól, hogy csak a másodlagos DNS szerver használhassa, ehhez hozzuk létre a /var/www/imscp/gui/public/.htaccess fájlt az alábbi tartalommal:
[size=large]1.2. BIND9 módosítása[/size]
Lépjünk be a bind9 config könyvtárába és hozzunk létre egy kulcsot a bind9 közötti kommunikációjához:
Felgyorsíthatjuk a generálást, ha elkezdünk gépelni össze-vissza a parancs kiadása után.
Ha elkészült a kulcs, adjuk ki az alábbi parancsot, hogy láthassuk a base64 kódolt kulcsot:
Szükségünk lesz a következő lépésnél.
Adjuk hozzá az alábbit a /etc/bind/named.conf.options fájl végéhez (options {} rész után)
Majd indítsuk újra a BIND9-et:
[size=x-large]2. Másodlagos DNS szerveren[/size]
[size=large]2.1. BIND9 módosítása[/size]
Adjuk hozzá a /etc/bind/named.conf.local fájl végéhez az alábbit:
Majd adjuk hozzá az alábbit a /etc/bind/named.conf.options fájl végéhez (options {} rész után)
Majd indítsuk újra a BIND9-et:
Teszteljük, hogy le tudjuk-e kérdezni a domain listát:
Ha megjelennek a DNS-zóna definíciók, akkor minden remekül működik és ideje beállítani, hogy automatikusan frissüljön a domain-ek listája. Ehhez hozzuk létre a /etc/cron.d/imscp_dns_update fájtl az alábbi tartalommal:
A létrehozása után 5 percenként frissülnek a DNS-zónák az éles szerverről. Ha mindent jól csináltunk, akkor a /var/cache/bind/ könyvtárban megjelennek a <domain>.db fájlok.
Lehet örülni
Display MoreOk; Despite the problem as mentioned in my previous post, which is already fixed in master, you are wrong here.
Should be
Please update to last master and after, do a reconfigure:
If you want, I can help you via teamviewer.
Thank you for taking care of this issue!
I have already solved it with updating the mysql.user table with right value.
When you choose the remote option for the SQL server, you are asked for the IP address of the remote SQL server and you are also asked for the hostname to use for SQL users created by i-MSCP.
What is the value of the parameter DATABASE_USER_HOST in your /etc/imscp1/imscp.conf file?
$ grep 'DATABASE.*HOST' /etc/imscp/imscp.conf
DATABASE_HOST = 10.0.0.10
DATABASE_USER_HOST = 10.0.0.10
Hello ;
I'll check.
You are normally also asked for SQL hostname to use. You entered what value for that question?
I changed the default "localhost" value to "10.0.0.10".
for example:
eth0's IP is 192.168.0.1 (external interface) -> set for i-MSCP IP address
eth1's IP is 10.0.0.1 (local lan interface)
remote sql server's IP is 10.0.0.10
i-MSCP version: 1.1.0-rc3
If "remote server" is being choosen at "SQL service" page, and I set 10.0.0.10 as SQL server address during the installation process, wrong value appeares in the host cell of the "dovecot_user" in mysql.user table. The eth1 IP address should appeare in the host cell instead of eth0, as at the other user's happen (vftp, roundcube_mail, pma).
Ok, no problem.
Today I have already found a workaround for disabling the MariaSQL removal.
If MySQL/MariaSQL had already been intalled on the host system and the "remote server" would be choosen on the "SQL service" page then the autoinstall will uninstall the local sql server.
This is normal or did I make mistake?