Yea, I assume he is done 
I have a copy at home, I will upload a copy if you like, but I was unable to get it to sync from an interworx box to an interworx box.
Thanks,
Clint
That would be great.
I’m going from Iworx box to non-Iworx (if all goes well – or at all … )
Thanks again.
JB
<bump>
If anyone has a copy of this script – it would be great to have here on the forums.
JB
Buehler … Buehler …
Really, I’d take it via PM, email, courrier pigeon, whatever … 
JB
OK … short of beating a dead horse here …
I’ve heard through the grapevine that some version of DNS replication will be built-in to the next release (point?) of IWorx … however, I’d love to get a head start on this.
I’ve got a second box built (CentOS 4) replicating manually the entries from a single IWorx server (DJBDNS). I’d love the aforementioned script so that I can get multiple servers syncing to this secondary (tertiary) server(s).
Is there no-one who’d be willing to re-post the original script (broken, orphaned or whatever) – even for archive’s sake? I’d love to get this automated sooner than later.
Regards,
JB
JayBean,
We will be releasing a BETA version of our DNS sync in the next (point) release. We’re lookin gto release in the next 2 weeks (uh oh, I gave a release date :D) and this feature will be “hidden” so folks don’t take it as non-BETA. Please contact me when the point release comes out and we’ll explain how to use the sync feature.
Chris
Fabulous answer.
Thanks for the reply, I’ll contact you once the release hits.
JB
ha ha ha chris that give a release date, incredible !!! 
:eek:
It DOES happen once in a while
haha, once in a while :D… and to be even more specific the point release will be out Thursday. It’s mainly a bugfix release but does have some oft requested goodies which we’ll detail in the changelog.
Chris
Did this hidden feature make it?
It did. Anyone wishing to use the BETA DNS sync between 2 iworx-cp boxes go to (after you login to nodeworx):
https://<your server>:2443/nodeworx/dns.php?mode=sync
You can then add “listening” servers to the current iworx-cp server which will grab dns info on a 5 minute basis and publish the dns data in conjunction with any location dns info.
Chris
This is sort of working nicely, almost…
I’ve just finished setting up 2 servers afresh with my new iworx licenses after falling in love at first sight on the 25th. I need to get a 3rd sometime soon.
I’ve added 2 zones and configured them on what I consider my primary dns server and set this up to publish to and listen for updates from what I consider to be my tertiary server, and vice versa.
However my “primary” doesnt seem to be publishing data to my “tertiary” however the opposite is happening. My “tertiary” is sending blank data back to my “primary”.
Any ideas?
hmm I recreated the setup and added a siteworx account and its synchronised okay.
However there is an interesting development if you look here: http://www.dnsreport.com/tools/dnsreport.ch?domain=digital-euphoria.net you’ll see what I mean
I’ve disabled synchronisation for the moment. I need my dns to work
I’m wondering if it wouldn’t be best to use the API to push changes to a persons “primary” server and have all subsequent nameservers refresh their data from the “primary” every 15 minutes to avoid mass record duplication which leads to dns breaking.
Their also needs to be some way to keep the serials synchronised across machines too.
LordOfLA,
What was your exact DNS setup with the sync tool? There should be no dup records if you’re doing a one to one sync and what you describe about setting up a “primary” and having it sync every so often is how the cur system works.
Chris
Chris,
I had my “primary” pushing updates to my third dns machine, as well as having the third push updates to my primary.
Wanting all 3 machines to have the same data if dns zones are being added on different machines I need the other 2 to get the data pushed over to them.
However the data pushed back to the primary includes what the primary already has and ends up being duplicated, rinse, repeat. It had got to the stage where tinydns just wasnt answering lookup requests due to the number of records in a potential response.
eg:
I have say ns0.digital-euphoria record on primary.
primary pushes that to tertiary which had no data but now has ns0.digital-euphoria.net record.
Tertiary sends that data back to primary. which merges in the new data and has a duplicate entry.
This gets pushed out to tertiary which merges in the information and now has 3 duplicate entries.
This gets pushed back to primary which now ends up with 5, etc…
It was amusing to watch until tinydns broke down and asked me just what it was I wanted it to do
I have say ns0.digital-euphoria record on primary.
primary pushes that to tertiary which had no data but now has ns0.digital-euphoria.net record.
Tertiary sends that data back to primary. which merges in the new data and has a duplicate entry.
This gets pushed out to tertiary which merges in the information and now has 3 duplicate entries.
This gets pushed back to primary which now ends up with 5, etc…
It was amusing to watch until tinydns broke down and asked me just what it was I wanted it to do
Actually that’s not how the system works so I’d like to check this out more if you have it setup still. It’ll never combine the polled data and pass it on (i.e. it’s not transitive). If box A is listening to only box B and box C is listening to only box B then box C will never have any of box A’s info. It was designed this way for just this “cycle” problemn you mention.
Chris
I had box A listen to and publish to box B and box b to listen to and publish to box A.
If there is a better way to make sure all 3 dns servers serve all the domains created on any of the 3 machines how would I go about it?
I can recreate the setup if you like and you can login to the boxes to watch.
I haven’t gotten my third iw-cp license yet so we cant check what happens with 3 machines just yet however.
Hi
Not sure to understand. Sorry.
I have 3 Iworx boxes.
But I have only 1 main dns servers located on BOX 1 (another instance of djbdns)
Today I do sync of dns data (data.cdb) from BOX2 and BOX3 to BOX1
So I have only one ns1 et ns2 servers for all my boxes (located on BOX1)
With this tool, how I should set it up ?
Enter in BOX1 then add BOX2 and BOX3 in BOX1’s sync tool
or
Enter in BOX2 and BOX3 's sync tools and add BOX1 ?
I think this is the last solution, isn’t it ?
Also does it sync the main interworx data.cdb (that is also sync to all IP on the same boxes) ? or do I have to define the IP of the instance of my djbdns ?
Thanks
Pascal
ps : the dns.php?mode=sync works on one of my box but not of the other (both are at 2.1.2 release level)