First things first to all of the SolidCP developers and contributors – a huge thumbs up and thank you for keeping the open source edition alive and well.
Since the upgrade to SolidCP 1.4.3 we are having problems with new DNS Zones that are created for Simple DNS 8 (Build 107). Editing of the zones is working fine so this is just a problem with new ones. When we upgraded to 1.4.3 from 1.4.2 we edited the SolidCP database and changed the SimpleDNS Provider to v8.x for our DNS Service. So far so good, we could edit zones although we now had to add a full stop at the end of the record but thats OK it at least works but when we create a new zone by adding a domain the zone file gets a bit messed up and you can see from the screenshot below.
Maybe this is caused by our setup of DNS server in SolidCP (which incidentally has not changed since it was setup in DotNetPanel) but basically we only have the 1 DNS Server configured in SolidCP as SimpleDNS takes care of creating and maintaining the zones on our secondary server.
We have defined the Primary and Secondary servers in SolidCP as you can see from the screenshot below but when the zone is created it takes these records and adds the users domain after each NS record and then adds another NS record for good measure for some reason. I tried adding a full stop to the end of the Primary and Secondary servers, by using the database as the portal would not allow it, but that did not work either and resulted in neither of the NS records being added. I also tried the information in this link but it did not have any effect https://solidcp.com/forum/question/how-to-setup-solidcp-with-a-simpledns-v6-cluster/
SimpleDNS Plus 8.x Provider Setup showing our Primary and Secondary servers are defined
This is how the zone gets created
Is this a known bug or is there something else we need to configure for 1.4.3?
I must say i don’t really work with SimpleDNS my self, so just to verify:
You use the SimpleDNS cluster method? or are you using Primary/ Secondary zones? (with primary / secondary method i would expect the “Secondary DNS Services” to list the other DNS Servers aswell).
Can you also verify your own DNS Server isn’t altering / inserting NS records? (i only ever seen that with MS AD DNS but it looks remarkably similar to your records).
“You use the SimpleDNS cluster method?”
I believe so yes, SolidCP is only configured to talk to our Primary server. After the zone file is created on our primary server (by SolidCP) SimpleDNS then communicates with the secondary nameserver without any intervention from SolidCP. This has been working without any issues for the last 10 years or so.
“or are you using Primary/ Secondary zones? (with primary / secondary method i would expect the “Secondary DNS Services” to list the other DNS Servers aswell).”
I am not 100% sure what you mean here, sorry.
“Can you also verify your own DNS Server isn’t altering / inserting NS records?”
I do not believe it is. It all worked great with SolidCP 1.4.2 and earlier versions. This only started to be a problem with the 1.4.3 release.
Is there anything else I can provide you with to help?
I have further looked into this report and there does indeed appear to be a bug in SimpleDNS 8.
There should be no need to add the extra . and it appears that due to this missing when calling SimpleDNS API it does presume to add the domain.
I have logged a bug for this so we can further fix this issue.
Are you able to use the V6 provider when you have the API V1 enabled in SimpleDNS?
Simple DNS 8 has a default TTL setting that you can set to whatever you want. Currently when I create a new domain through SolidCP, it creates 3 hour (10800) TTLs by default. I see the SOA settings in SolidCP and that works but it is missing the Default TTL field.
Is it possible for you guys to have SolidCP pickup the default TTL setting we set from Simple DNS? Or be able to set that default TTL setting through SolidCP?
Or even better, be able to set a default TTL in the Simple DNS provider settings and also be able to edit each individual DNS entry’s TTL. That would enable us to sell DNS services by itself!
- Views526 times
- Answers5 answers