KNL-BSW
06-24-2004, 12:04 AM
Please take into account I am posting this being frustrated and upset. I probably should wait for 4PSA's response, but I want to post as I need some help. And I will post the eventually outcome of this.
We have been working on our own Centralized DNS solution, but with the release of 4PSA's DNS Manager we thought our woes were solved.
Upon contacting sales one of my primary concerns was whether it would pull DNS from Plesk for Windows. Here is the response:
"Yes, of course. You can get the Zones from absolutely ANY DNS server on the market."
Now hearing this I was overjoyed to find a product that could solve all of our problems. We worked out the details and obtained it for testing and configuration.
Now the problems begin. First they tell me I should install to a Clean Server, but the directions are more aimed at installing to a Plesk Server.
Fine, we get past that and get it installed. Clean server of course since the license is IP based.
Next come to find out register_globals has to be on. Considering it is a fresh server and the install directions didn't say this it hadn't been turned on. Figured this one out on our own.
So, we have it installed and I start reading up on the integration system. I now discover that all the integration files are for linux so I post a ticket and request info. I'm told I have to create the zone file. So, now we are developing again. Well, I figure we can convert the .sh to a win file, which is where we are still having problems, and proceed with the linux side.
Okay, after getting the files moved over to server 1 and run in cron I go back and configure 4PSA to remote udpate.
Great, it grabs one zone. I proceed to go through and set it up on the other servers, going to have to do it anyways, and it still doesn't update.
Well, I think maybe it needs a kickstart. So, after further reading I download the created files and import them into 4PSA DNS.
Zones are there, named is running, cool. Now the test. I go add zones to one of our Plesk servers and they don't update. So I put in a ticket. After over 14 hours I get a response saying they are there and we had been back and forth a few times and I gave them login info for the server and the management interface. So, I login see the zones there an the total zones increased. Good, it works.
Now, I add a few more to test and no go again. So I post to the ticket and get told cron is broke and he ran it from the command line. So I run it from the command line, again, no additional new zones are added even though they are in the download file.
So, here I am. 1 DNS Manager that requires manually insertion of all zones and will not integrate with Plesk for Windows without a whole new file. :bawling:
Opinions would be nice.
We have been working on our own Centralized DNS solution, but with the release of 4PSA's DNS Manager we thought our woes were solved.
Upon contacting sales one of my primary concerns was whether it would pull DNS from Plesk for Windows. Here is the response:
"Yes, of course. You can get the Zones from absolutely ANY DNS server on the market."
Now hearing this I was overjoyed to find a product that could solve all of our problems. We worked out the details and obtained it for testing and configuration.
Now the problems begin. First they tell me I should install to a Clean Server, but the directions are more aimed at installing to a Plesk Server.
Fine, we get past that and get it installed. Clean server of course since the license is IP based.
Next come to find out register_globals has to be on. Considering it is a fresh server and the install directions didn't say this it hadn't been turned on. Figured this one out on our own.
So, we have it installed and I start reading up on the integration system. I now discover that all the integration files are for linux so I post a ticket and request info. I'm told I have to create the zone file. So, now we are developing again. Well, I figure we can convert the .sh to a win file, which is where we are still having problems, and proceed with the linux side.
Okay, after getting the files moved over to server 1 and run in cron I go back and configure 4PSA to remote udpate.
Great, it grabs one zone. I proceed to go through and set it up on the other servers, going to have to do it anyways, and it still doesn't update.
Well, I think maybe it needs a kickstart. So, after further reading I download the created files and import them into 4PSA DNS.
Zones are there, named is running, cool. Now the test. I go add zones to one of our Plesk servers and they don't update. So I put in a ticket. After over 14 hours I get a response saying they are there and we had been back and forth a few times and I gave them login info for the server and the management interface. So, I login see the zones there an the total zones increased. Good, it works.
Now, I add a few more to test and no go again. So I post to the ticket and get told cron is broke and he ran it from the command line. So I run it from the command line, again, no additional new zones are added even though they are in the download file.
So, here I am. 1 DNS Manager that requires manually insertion of all zones and will not integrate with Plesk for Windows without a whole new file. :bawling:
Opinions would be nice.
