Re: Too many domain controllers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello Pierre,

Get back the programming company and let them rewrite the programs. You can not really play around with DNS for this. So the way with shutting down one DC and find the problems is better option. ANd then change if possible the program's. If the company doesn't exist anymore i would start thinking to get rid of that bad written software and find better solutions.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Hi we inherited an active directory design that we are looking to
revamp -in essence we have a total of 6 domain controllers for a user
community mostly for application authentication and should only need 4
maximum.

The problem is we have dozens of applications which have been written
in the past by external contrctors and which have been known to be
configured to point to a single domain controller instead of to the
entire domain.

We are adfraid that if we start shutting down some of these domain
controllers, that we will break the application from working.

Some ideas we have are:

1.- Shutdown one domain controller at a time and see which application
stops authenticating.

2.- Shutdown the corresponding domain controller we want to get rid of
and crreate a cname in DNS to point that "shutdown" dc to the domain.
i.e. olddc CNAME domain.local

Can anyone think of another way to address this issue while minimizing
the impact in the user community.?

We are planning to decommision 2 out of the 6 dc's.



.

Relevant Pages

  • Remote Branch DC wont Replicate With Corporate DC
    ... Active Directory could not resolve the following DNS host name of the source ... domain controller to an IP address. ... 'Event' is not recognized as an internal or external command, ... operable program or batch file. ...
    (microsoft.public.windows.server.dns)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... area of DNS it was missing the CNAME entry with the GUID ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... one of the domain controllers the active directory DNS zone ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... one of the domain controllers the active directory DNS zone ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... DNS it was missing the CNAME entry with the GUID for the other ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)