Hello,

I would highly recommend not to ever use AD DNS for Public domains.

As you will need to remove all root zones and disable recursion (forwarding) to keep your DNS Server safe from being attacked or worse: used to attack others.

However when you do this every domain joined server on the active directory using those AD DC's can no longer connect to the internet (no dns resolving).

In addition you will also have no control over NS Servers, as Active Directory will always push it's AD FQDN NS's.

However for your question: if one domain works but not the other; do you have the hosting plan set to a Virtual Server, where you have included both DNS servers in the virtual server settings? as this generally would mean one DNS server is working correct with SolidCP but the other isn't. (configurational / permission based issue).

In general i would always use 1 primary dns server solidcp talks to and only have the other dns server(s) set as secondaries inside the DNS Configuration.

Regards,

Marco

Hi Marco,

Yes I actually read your post regarding AD DNS being public. I am using the DNS on the web server (not the DC) for public domains.

1. Is this the recommended setup?

I got past the earlier problem, the reason behind it was because i had Microsoft DNS Server 2012+ (DC DNS) and  Microsoft DNS Server (Web Server DNS) on the same virtual server. Removing the Microsoft DNS Server 2012+ solved the problem an DNS was activating.

But now it seems adding an organization produces an error:

==================
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'CREATE_ORG' task on 'cyclesoft' ORGANIZATION ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Runtime.InteropServices.COMException: Unknown error (0x80005000) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Exists(String path) at SolidCP.Providers.HostedSolution.OrganizationProvider.OrganizationExistsInternal(String organizationId) at SolidCP.Server.Organizations.OrganizationExists(String organizationId) --- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SolidCP.Providers.HostedSolution.Organizations.OrganizationExists(String organizationId) at SolidCP.EnterpriseServer.OrganizationController.CreateOrganization(Int32 packageId, String organizationId, String organizationName, String domainName) --- End of inner exception stack trace --- at SolidCP.EnterpriseServer.OrganizationController.CreateOrganization(Int32 packageId, String organizationId, String organizationName, String domainName) at SolidCP.EnterpriseServer.esOrganizations.CreateOrganization(Int32 packageId, String organizationID, String organizationName, String domainName) --- End of inner exception stack trace ---

==================

2. Any ideas where to start on this one?

Thank you for your time

I added the Microsoft DNS Server 2012+ back to the virtual server and removed it again. The error went away.

Thank you.