Thought I would share this with the community considering that SimpleDNS 8 has been released and boasts many new features – those that are most notable are the new API and compliance for DNSFLAGDAY.
We were fortunate enough to have one of our clients assist with the development after we were not being able to allocate development resources internally due to other commitments.
The changes included within SimpleDNS 8 include bug fixes dating back from SimpleDNS 5, 6 and resolve issues such as long string format for records such as txt, additional record types including CAA records, and many more.
There are one or two changes which I need to feedback and have added to the latest fix and as soon as these are done I’ll post a manual update guide for those that want to implement the changes we have made in the event that the next version of Solid is only pushed out in a month or two.
Is there any update on this? We are having to process more and more DKIM requests manually at the moment so we are eager to implement this update when it is released.
These changes have been approved for the next release of solid so the file provided here is a hack in the mean time.
Use at own risk, and make sure that you run backups prior to any change.
Where you see
C:\SolidCP please read that as your install directory.
1. Download the zip file
2. Extract the zip file
3. Copy the
web.config files from both Enterprise Server and Server directories to a safe place. Take note of which one came from which directory this is very important
4. Delete the three directories and their contents from
5. Copy the three directories from the extracted zip file to
6. Copy and replace the
web.config file in Enterprise Server and Server with the ones you backed up earlier.
7. Execute the following SQL command on the solidcp database:
INSERT INTO [dbo].[Providers]([ProviderID], [GroupID], [ProviderName], [DisplayName], [ProviderType], [EditorControl], [DisableAutoDiscovery]) VALUES (1901, 7, N'SimpleDNS', N'SimpleDNS Plus 8.x', N'SolidCP.Providers.DNS.SimpleDNS8, SolidCP.Providers.DNS.SimpleDNS80', N'SimpleDNS', NULL);
iisreset from an elevated powershell/command prompt.
Next stable release of SolidCP has now been scheduled in for end of April.
(Countdown is visible on the SolidCP homepage).
It will contain the Simple DNS 8 provider thanks to Jade and his client.
Thank you ever so much on your work on this… It was one of the things I was going to look at developing so really happy to see it already done 🙂
A small word of caution to anyone looking to implement the hack though… It borked my install. Fortunately it was a fresh full server install so wasn’t important but be real careful doing this… make sure you can roll back if any issues. That’s certainly not meant as a criticism in any way of the excellent work done on this.
No problem at all,
Can you advise as to what broke and why as this may assist us in updating the code / instructions
Sorry Jade, I wasn’t able to work it out (the portal wouldn’t load at all and I just got the standard error message… stupidly I’d only backed up the web.config files and not everything else and unfortunately there were no clues in the event log and tbh I’m not yet familiar enough with SolidCP to figure it out (although I have quite a bit of experience with WSP so aim to rectify that ). In the end I destroyed the server and I’m trying again with a fresh install… will let you know how I get on.
Trying to post this again… something keeps stopping it from posting…
I did a fresh install and ran through the process as described above but have the same results.. Its an issue with the portal communicating with the Enterprise Server and I see this but as yet I’ve been unable to work out what the problem is…
Haven’t managed to work out what is wrong 🙁 Guess I’ll just have to wait for the next release or get up to speed on building from source (the build docs are very out of date and I’ve also struggled with getting the versions of everything right to even get the build working) 🙁
- Views719 times
- Answers9 answers