locked
An active directory domain controller cannot be contacted RRS feed

  • Question

  • Hi,

    I built a server 2019 domain controller. I successfully promoted the server to domain controller. I also built a windows 10 computer to use as a workstation. 

    When I try to join the windows 10 computer to the domain I get error :

    "An Active Directory Domain controller (AD DC) for the domain "domain" could not be contacted."

    DNS was successfully queried for service location (SRV) resource record used to locate a domain controller for domain "domain":

    The query was fo SRV record _ldap._tcp.dc._msdcs.domain.com

    The following domain controllers were identified by the query:

    (no Active Directory Domain Controllers found)

    However no domain controllers could be contacted.

     

    Please advice I am trying to build a lap on my laptop and I am using public wifi for connection.

    Thanks,

    Senait


    Saturday, March 14, 2020 7:28 PM

Answers

  • Domain controller and problem member must have the static ip address of DC listed for DNS and no others such as router or public DNS

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 8:04 PM
  • Hello Senait,

    Thank you for posting in our TechNet forum.

    As Dave and Marcin mentioned, we had better set a static IP address for the DC and we had better add DNS role in the DC, so the DC is also a DNS server.

    For example, in my lab,

    1. Here is the IP address of my DC and the DC is also a DNS server (domain name is b.local).

    2. Here is a member server in b.local domain.
    We should set the IP of the DNS server (that is domian controller's IP address) as Preferred DNS server of this server.

    3. Then we can try to join the client to the domain again.



    Best Regards,
    Daisy Zhou

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 16, 2020 2:46 AM
  • You have to use a DNS server which is hosting the zone corresponding to the namespace used internally by your AD. Typically, this is the DNS server installed directly on the domain controller which relies on AD-integrated zones.

    As Dave has pointed out:

    1) assign static IP address to your DC

    2) point the computer you are trying to join to the DC as its primary and only DNS server

    hth
    Marcin

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 9:45 PM
  • That isn't possible to do. Member must be able to contact internal DNS server on your domain.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 10:56 PM

All replies

  • Domain controller and problem member must have the static ip address of DC listed for DNS and no others such as router or public DNS

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 8:04 PM
  • Thank you, I was trying to join the domain on a public DNS server.
    Saturday, March 14, 2020 8:55 PM
  • You have to use a DNS server which is hosting the zone corresponding to the namespace used internally by your AD. Typically, this is the DNS server installed directly on the domain controller which relies on AD-integrated zones.

    As Dave has pointed out:

    1) assign static IP address to your DC

    2) point the computer you are trying to join to the DC as its primary and only DNS server

    hth
    Marcin

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 9:45 PM
  • That isn't possible to do. Member must be able to contact internal DNS server on your domain.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by senizkibret Thursday, March 19, 2020 7:03 PM
    Saturday, March 14, 2020 10:56 PM
  • Hello Senait,

    Thank you for posting in our TechNet forum.

    As Dave and Marcin mentioned, we had better set a static IP address for the DC and we had better add DNS role in the DC, so the DC is also a DNS server.

    For example, in my lab,

    1. Here is the IP address of my DC and the DC is also a DNS server (domain name is b.local).

    2. Here is a member server in b.local domain.
    We should set the IP of the DNS server (that is domian controller's IP address) as Preferred DNS server of this server.

    3. Then we can try to join the client to the domain again.



    Best Regards,
    Daisy Zhou

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 16, 2020 2:46 AM
  • Hi,
     
    I just want to confirm the current situations.
     
    Please feel free to let us know if you need further assistance.
     
    Best Regards,
    Daisy Zhou

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 18, 2020 1:33 AM
  • Thank you so much. The problem was I was trying to add it to a public DNS server. I no longer have the issue.

    Thanks,

    Senait

    Wednesday, March 18, 2020 2:57 PM
  • Thank you so much. The problem was I was trying to add it to a public DNS server. I no longer have the issue.

    Good news, please don't forget to mark helpful replies as answer)

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, March 18, 2020 3:48 PM
  • Hi,
    Thank you for your update. I am so glad that the problem has been resolved.

    It is perfect if we can share our solution.

    Have a nice day!



    Best Regards,
    Daisy Zhou

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 19, 2020 1:35 AM