Hi I have a problem with configuring dns master and slave. I have 2 servers with 2 ispconfig installations. They share a mysql database with is configured in master-slave-master. Which means that they use the same database in fact. Also, the servername can only be given once. Now when I want to configure dns master on server1 it is not possible to configure to configure server2 as a slave. The thing is that I also use ultra-monkey so that apache is load-balanced on the internal network. Example: Apache has ip 192.168.1.246 (load balanced) = www server1 has ip 192.168.1.239 (server1.xyz.nl) wanted as nameserver1 server2 has ip 192.168.1.238 (server2.xyz.nl) wanted as nameserver2 I wanted to use your godaddy howto but this is what I stumbled upon: Let's say that I have for the ISP domain name xyz.nl Step 1 (page2 godaddy) I enter at title and SOA: xyz.nl with ip-address 192.168.1.246 step2 I created the A records: www = 192.168.1.246 , server1=192..239, server2=192..238, mail=192..239. step 3 I created MX: no hostname, priority 10. mailserver=mail.xyz.nl All = fine till now. If I now go to server2 in ispconfig...it ofcourse shows me the same thing (shared database mysql). How can I make this the slave dns server (since it has the same server-name etc). Should I maybe should work with cname ? I hope I could explain this clearly, and I hope you can help me Thanx Randy
Why do you configure ISPConfig like this. The software is not intended to run 2 instances from the same database ind it wont work because the status fields where deleted by two processes. ISPConfig supports master / slave DNS outr of the box when you have 2 separate ISPConfig servers.
Because it is a bit odd to supply webservices to others (which they might find very important) without being able to supply redundancy, don't you think. This way I have everything double. I have solved it by using regular cron jobs. It seems to work okay. Rany
But what you did is not redundant as you use the same mysql database for both instances. If you have two independant ISPConfig instances with the builtin Bind secondary / slave functionality as I described, its a redundatnt setup.
But what you did is not redundant as you use the same mysql database for both instances. If you have two independant ISPConfig instances with the builtin Bind secondary / slave functionality as I described, its a redundatnt setup. Maybe I described it wrong. There are two servers with two separate mysql servers which are interconnected in a slave-master master-slave setup. The ispconfigs are thus also separate but this way they have access to the same info, which is the reason why a slave master bind is not possible thru ispconfig(which wasn't intended in the first place, I know). But now if one server dies, the services continue on the second server nicely (including ip-adresses, mail ftp etc.) Not bad, what you have given us. I thank you, because it gave me a chance to learn linux (debian) in about six weeks time (I'm a netware guy originally). Still learning ofcource.....
You will most likely get problems with the ISPConfig update script. These problems are race conditions and you will get them when your server comes under load. Thrust me, I've written parts of this code and I know what I'am talking about
Thanks, Maybe you won't believe it, but somehow I have more trust in the advice that you give (and have given in the past) then you might think. I'll start my shutting down the ispconfig system on the second server, since it isn't needed as long as the first server is in the air, and it will only be needed to create/modify sites while the first server is down.... Everything is replicated automatically anyway. Good tip, from the guru herself... Respect ! R
