Dotnetpanel Forums

Hello guys,

We apologize for the inconvenience but we've found that the current Simple DNS provider implementation in several cases is incompatible with the ver. 5 because of the new DNS record format introduced.

Due to this we considered to support these changes in the upcoming 2.4.2 version. We expect this version is available by the middle or end of May.

Thank you for your understanding.

Middle or end of May!!!

If this is the case then we have real problems as we have spent over $1,200 on DNP licenses and support to put this into production in the next couple of weeks.

The SimpleDNS API isn't that hard to work with and we built a solution ouselves before that works with our own Domain Name Registratuion system and SimpleDNS and took less than a day to build in support for adding DNS records into SimpleDNS also we have seen no changes to the way the API works between 4.x and 5.x.

 Taking 4 to 6 weeks to come up with a fix is extreamly exesive and don't really give much confidence in your software if something which could be fixed quite quickly will take you 4 to 6 weeks to fix leaving anyone using DNP in production totally screwed.

If this is the case then we would need to look at having this refunded as look at other Control Panel solutions as this amountt of time to fix a bug like this is outragious and can not wait months to put DNP into production.

We understand your point and really apologize for this inconvenience but in some cases solutions aren't so simple as they might look at a first sight. Our team does its best in order to deliver critical fixes as soon as possible and the dates mentioned assume that all fixes will be tested and verified in order to be sure they work as expected and provide reliable solution.

Of course these dates wouldn't intend you to make a refund or even start looking for another solution as we honor each client and every business that relies on our products/solutions.

Thank you for your understanding.

Pavel

Is there any chance of getting a hotfix for this or similar? As I've said we have customers losing their dns-zones due to this. I can disable the dns-editor manually for troubled customers but still it takes a day or two to recognize broken zones. Then we have customer supports editing dns-zones via administrative users whom I cant disable dns-zone editing for. The worst part is that the zone looks normal in DNP while its not working in SimpleDNS so there is no way for us to recognize when a zone gets broken. We have to wait for customers calling in complaining about their domainname not working.

This is a quite serious issue for us, I hope we can find a solution to the problem.

Regards

Daniel

 Sorry but are slightly loosing confidence in your software as found a number of bugs that mean we can not put DNP into production, we have also paid $200 for support and raised allot of the issues with support and have after 3 days of waiting for a reply had back the today (Monday) the following response from support, with no explanation just the following:-

 Sorry for delay, can we continue on Tuesday?

 At the moment from were we are this really doesn't look good as are moving from another control panel to DNP due to bugs not being fixed and bad support only to find after a spending quite some time working with your API and spending allot of money that we are now in the same boat that we were in before.

So we now have 2 control panels from 2 vendors both with bugs, both with very slow support, and both not production ready.

It's starting to look like if you want to be a professional web host and look professional with bugs fixed ASAP that the only way forward is developing a control panel inhouse. 

Daniel,

We've performed a deep research prior and found out that it's absolutely impossible to deliver a quick-fix or a temporary solution. We're willing to deliver this fix as soon as possible but due to the breaking changes it'll lead it can be considered as a "quick-fix".

Thank you for your understanding.

 Very sorry but if this is the case can not wait till May to put DNP into production and the beceuase of the bad response times to support tickets will need to ask that we have a refund.

Ok Pavel, thanks for the reply. Please contact me when/if you have something I can use prior to 2.4.2.

borg:

 Very sorry but if this is the case can not wait till May to put DNP into production and the beceuase of the bad response times to support tickets will need to ask that we have a refund.

 Could you please let us know who we need to contact to have a refund?

We are sorry also but if you change your mind please do not hesitate to contact us anytime.

You can drop your request at sales@dotnetpanel.com with the order and receipt details.

Thank you for your understanding.

danielh:

Ok Pavel, thanks for the reply. Please contact me when/if you have something I can use prior to 2.4.2.

Daniel,

Thank you for your understanding. We'll update you as soon as any solution is available.

Thanks.

 Have put in a request for a refund, will this take 4+ days like your paid support for you to reply? as you currently have over $1,000 of our money to refund.

At the moment I am not happy with DNP, this issue was raised over a week ago and it has taken you a week to come back with a 6 week time scale to fix this!!

How can any business rely on DNP when it is run so unprofessionally?

Thanks to this week delay I have had my whole team working on DNP to intergrate using it's API with our own systems so that we could launch a hosting product based on IIS 7 over the next couple of weeks. Thanks to this I have lost 1,000's. 

Your sales guys responded within hours even at the weekend and were positive about all our questions, we now start using your software to find it is not production ready, has quite a few bugs, and your slow support and bug fix times are some of the slowest I've seen. What an expensive mistake DNP has been.

Still at least we found out this before getting DNP into production, just annoying that there are still software vendors around that think that this level of service is acceptable.  

Bruce,

Please, no worries! We've already refunded both your orders.

We always encourage customers to perform DNP evaluation before purchasing and we can issue any number of licenses for 30-days use.

 Thank you for the refund.

Did evaluate the software before purchasing DNP and new this issue also existed this time last week. What we were not aware of was that it would take more than 4 days to respond to paid support and that it would take so long for bugs to be fixed. Expected to have this issue resolved by now, rather than taking this long to give a 4 to 6 week time scale to fix it

Just really annoyed that so much time and money has been invested into DNP as a solution and now back to square one.

The thing which really seemed bad is that we raised support questions on this which we paid for and after 3 days only had a response syaing

'sorry for the delay can we will continue this tomorrow?' 

Not even an explanation why you can not reply till tomorrow or even a quick attempt at replying to some of the questions raised. When you depend on software like control panel software for your business and also pay $200 for support you expect/need a more professional and faster support time.

Any word on the status of a fix for this? This seems like a bit of a long time to fix something that should be relatively simple. Mid to end of May is way too long to wait. Almost as bad as Helm saying that Windows 2008 Support would be ready "sometime in Q3" 2008.

Thanks

Guys,

Did you try to export and import the zones again? Maybe that is resetting the wrong format. I have manually checked all my zones after upgrade to v5 (about 100) and modified them so they have the correct format. After that i have no problems whatsoever with updating or creating zones through DNP.

Main problem is the update of simpledns v4 to v5 as it seems; maybe those guys can help?

 Frans