none
Unable to Join to Domain RRS feed

  • Question

  • Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "ServproSSpringfield.com":

    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.ServproSSpringfield.com

    Common causes of this error include the following:

    - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

    10.1.10.203

    - One or more of the following zones do not include delegation to its child zone:

    ServproSSpringfield.com
    com
    . (the root zone)
    Saturday, September 29, 2018 2:06 PM

All replies

  • Hi,

    This error message simply means your computer was unable to find the Active Directory Domain Controller, so you need to tell your computer where to find the DNS server.
    ADD domain ip in preferred dns name on client pc/server and check


    Before connecting your computer to domain, make sure you have spedified the correct IP address of the domain DNS server (if you're using Active Directory-integrated DNS, it would be the IP address of your DC) as the prefered DNS Server in Network and Sharing Center, then try again.

    Also, verify if nothing works,

    1. Check network connectivity (ping from both ends)

    2. Check DC IP and specify the same (manually) in preferred DNS field on client machine

    3. Look for any settings which could block client-DC connectivity (like firewall, antivirus etc.,)

    4. Ensure netlogon service is running on server

    5. (on client side) Navigate c:\windows\debug\debug.txt & look for error

    5. If still issues, Go to DNS server-> create new SRV record under your domain: by choosing - new other record - select SRV in the list service: _ldap, Protocol: _tcp,  (other options are default) & specify <IP address of DC>

    Best Regards,

    Rafiul

    Mark if the post is helpful

    Sunday, September 30, 2018 6:51 AM