Two servers , same domain

[KKK666]

I currently have a domain called test.local configured on a server (called test1) running Windows Server 2008.
This server manages users, computers printers, etc. And so far so good.
Now I would like to configure via the dcpromo.exe tool a second server called test2 that belongs to the same domain and that has the ability to manage the users of the test1 server when the test1 server remains down or fails. So I configured via dcpromo.exe the test2 server as “existing forest” and “add domain controller to an existing forest.”.
All users and computers have been reported correctly in test2 server, but if I turn off test1 server I no longer have a connection to the Internet and test2 server informs me that the test.local domain no longer exists.
I definitely messed up something in the configuration.
Can anyone help me?

 

[ChatGPT]

It sounds like you're trying to set up a second domain controller (DC) for redundancy in your domain test.local, but you're encountering issues when the first server (test1) is offline. Let's break down the scenario and see what might be causing the problem.

Key Points to Consider:​

1. Active Directory Replication: Ensure that the second server (test2) properly replicated all necessary data from test1. This includes not just user accounts but DNS configurations, which are crucial for domain functionality.
2. DNS Configuration: When you turn off test1, if test2 is unable to resolve names or find the domain, it could be due to DNS issues. As a domain controller, test2 should have a DNS server role installed and configured correctly to point to itself as a DNS server. If test2 is set to use test1 as its DNS server, it won't be able to resolve names when test1 is offline.
3. IP Configuration: Check the IP configuration on test2. Make sure it has a static IP address and that its DNS settings are pointed to itself (or other available DNS servers, if applicable). This ensures it can resolve domain names even if test1 is unreachable.
4. Domain Controller Roles: Verify that test2 has taken on the necessary roles to be a functional domain controller. You can check this using tools like the Active Directory Users and Computers console or the Active Directory Sites and Services management console.
5. Network Connectivity: Confirm that there are no network issues preventing test2 from connecting to the Internet or other network resources while test1 is offline.

   Recommendations:​

   • Check the DNS Settings: On test2, ensure that the preferred DNS server is set to its own IP address.

• Force Replication: You can use the repadmin /syncall command to force replication from test1 to test2. Check for any replication errors.
• Review Event Logs: Look in the Event Viewer on both servers for any errors or warnings related to Active Directory and DNS that might give you more clues.
• Diagnostics Tools: Use tools like dcdiag to run a health check on both domain controllers. This will help identify any issues.

  Summary​

  You likely have a DNS misconfiguration or replication issue. Once you ensure that test2 can operate independently with proper DNS settings, you should see it handle requests even when test1 is turned off. Feel free to ask for further clarification or assistance!