.net - Missing AD server makes website go down -


In our CMS solution we have a module that is to handle integration for an AD, a standard connection string in the Web uses it. Config The client has setup two AD-servers and regularly takes them down for maintenance once. Unfortunately, the AD-module only allows connections on an AD-server and when the server goes down the website also goes down.

As I have seen, there are three ways to fix it:

  1. The code of AD-modules will be used to reuse the code for using many AD-servers. To write.
  2. Install a local AD-server on the web server that is duplicated from two others.
  3. Create a solution that acts as a front for AD-server, all the ways to connect to one that is running.

I have ended one and two options for various reasons and now I have only left three numbers.

Any thoughts?

Active Directory is already "out of the box" A "cluster" system (a multiple master system ). It depends on the DNS, for this there is no virtual IP address.

Let's say that two "Active Directors Server" (called domain controller or DC to reduce) have DNS-names server01. Customer.local and server02.customer.local

In this way, what you should do, only "customer.local" (not a server name, in the connection settings section of your "AD-Module" software) Just specify Active Directory Domain).

The web server will then be connected to either server01 or server02 or whatever is above the two and will run whatever domain controller will use in Active Directory "Cluster" feature to connect online Used to be.

Do not use an IP address or exact server name. And make sure that the web server is installed to use two domain controllers in the local IP settings as primary and secondary DNS. (This helps if the web server is in the same domain, as the domain controllers are servicing ...)


Comments

Popular posts from this blog

MySql variables and php -

url rewriting - How to implement the returnurl like SO in PHP? -

Which Python client library should I use for CouchdB? -