read that...
http://forums.cpanel.net/showthread.php?s=&threadid=23569
That won't fix your problem will give you some ideas of to why things get whacked with dns clustering.
I made some perl scripts to do my own dns clustering works this way.
I kind of do it like in that post above but it isn't automatic.
I just use a cron to update the dns every few hours.
http://forums.cpanel.net/showthread.php?s=&threadid=23569
That won't fix your problem will give you some ideas of to why things get whacked with dns clustering.
I made some perl scripts to do my own dns clustering works this way.
I kind of do it like in that post above but it isn't automatic.
I just use a cron to update the dns every few hours.
I have 3 servers in the cluster syncing each other ns1, ns2, ns3.
Now and then, when adding a new zone, i get duplicate entries in named.conf only on the server which runs ns3....
Now and then, when adding a new zone, i get duplicate entries in named.conf only on the server which runs ns3....
How do you have them syncing?JC said:I have 3 servers in the cluster syncing each other ns1, ns2, ns3.
Now and then, when adding a new zone, i get duplicate entries in named.conf only on the server which runs ns3....
Option 1
ns1 to ns2 and ns3
ns2 to ns1 and ns3
ns3 to ns1 and ns2
or
Option 2
ns1 to ns2
ns2 to ns1 and ns3
ns3 to ns2
I set my like option 1 above and sometimes get the duplicate problems. I was thinking about moving to option 2. It should have the same effect - IF ns2 will relay between the other 2.
