I don't think anyone has worked on SimpleDNS for years.
When reported on the forum i don't think anyone really noticed the bug report neither (as that really should be done in Github).
in the 1.4.8 to 1.4.9 update it did get set to the later framework version and a new Newtonsoft.json version but thats really been the only changes to the simpleDNS project as far as i am aware.
I am not sure how that can result in breaking simpledns and would require some further investigation.
Things we did test and work on is PowerDNS, Bind and MS DNS.those are confirmed fully working incl new features such as TTL per record
Only known bug is with MS DNS and long dkim records, as wmi and ps do not pass the required line breaks which means it can't write only read long dkim records for MS DNS
Regards,
Marco
@m-tiggelaar So i just create an account at github and submit bugs here right?
@enguard That is generally best.
Now i am a bit more active again so i tend to relay things from forum to other dev's and contributors (so this bug i also reported).
However if you report it directly in Github it is not dependant on a man in the middle to relay the bugs but it lands directly in de developers area.
@enguard Thanks!, it's already got a fix pushed just a little earlier based up on the report: https://github.com/FuseCP/SolidCP/commit/f8a24da51fbc31966f2b5be9946c79ebdf435a58
We plan to push out a 1.5.0 update within the next few working days that includes all sm, simpledns, and hopefully me reported issues (me is pending on dev license).
@m-tiggelaar will it be a 1.5.1 update? Or are you simply overwriting the current download files?
@enguard It will be simply overwriting current files for now (just a few minor fixes isn't worth pushing out 1.5.1 just yet, however if there's a bit more added i will opt for releasing another update in full).
@m-tiggelaar Great! please let me know when I can download an updated manual-update.zip file, thanks!
