Dotnetpanel Forums

It should work when zones are created from DNP and then updated from DNP only. Give it a try.

Paul:

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.

Hello!

Are You still planning to release 2.4.2 version in this month?

Regards

It's planned for June 3rd and it has new SimpleDNS provider.

 to migrate from SimpleDNS 4.x provider to 5.x I should only change ProviderID in EnterpriseServer DB (Servides table) from 9 to 28 ?

Any word on how to upgrade the provider?

Regards

Daniel

Hi.

Could you provide exact scenario of your migrating?  

Hi

Please read this thread? Im sorry for the rude answer but I belive this thread is the reason why you implemented a new provider for v5. We have all upgraded SimpleDNS v4 to v5 before you implemented the new provider and that left us with corrupt dns files. Now I wonder how do I start using the new provider?

1. Open service properties page in DNP and remember ServiceID from URL query string.

2. In Enterprise Server database table “Services” locate the record with ServiceID from first step.

3. Change ProviderID to 28 (old value should be 9).

4. Edit and update service properties in DNP.

Regards,

 Frans

The new provider DOES NOT work. It corrupts existing records and does not read the name portion correctly. Please fix and test. Thanks

DotNetPanel guys.  Keep in eye on the new beta for SimpleDNS 5.1  will have some API modifications.

http://www.simpledns.com/beta.aspx

New and updated HTTP API commands

• New "getconfig" and "updateconfig" commands - retrieves/updates the Simple DNS Plus configuration (Options dialog settings).
• New "addaliaszone" command - adds a new zone using the same zone file as an existing zone.
• New "aliaszonelist" command - lists all zones using the same zone file. XML or plain text format.
• New "comment" parameter added to "updatehost", "addrecord", and "updaterecord" commands for specifying record comments (no longer adds automatic comment "Added via HTTP API at ...").
• New "format" parameter added to "zonelist" command. The value can be either "xml" or "text".
  This replaces the "listtype" parameter which still works but is now deprecated.
• New "suspendzone" command - see "Suspending Zones" above.
• New "resumezone" command - see "Suspending Zones" above.
• XML version of the "zonelist" command has new "suspended" attribute - see "Suspending Zones" above.

proeder:

1. DNP passes a wrong zone file content to SimpleDNSPlus
   • the soa responsible person is missing
   • parenthesis at the end of the soa record are missing
   • the ttl is placed in front of the ns record, sdns does not seem to like that
2. When creating a new website for a given domain, the very same thing is happening because DNP updates that zone while creating the website
3. When creating a website, DNP is updating the zone but
   • it does not check if there already are records matching the record type, it simply adds new records
   • it should check if there already is a record that needs to be updated rather than added
   • this can cause double * / A records pointing to different locations

We are experiencing all of the above problems as well and we are running DNP 2.4.2 with SimpleDNS v4.00.07.

Should we upgrade to SimpleDNS 5 or will this just make a bad problem worse?!?

Feodor, is there any update on this bug?

Please let me understand something here. You have installed SimpleDNS 4 and then switched provider (like shown above) to SimpleDNS 5, right?

We tried the 5.0 provider on SimpleDNS 5 and it really hosed things up. Had to revert back.

Are there any errors? Is it possible for our engineers to take a look at these issues in your environment?

No errors in DNP, just hosed reocrds, records with no names, add a record and 4 others get deleted. Just some serious errors.