none
Cannot join domain. RRS feed

  • Question

  • About a month ago I was not able to join the domain mk1. I get the below error. Any help on figuring out how to fix will be great.

    The domain name "MK1" might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

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

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

    The following domain controllers were identified by the query:
    mkdc1.mk1


    However no domain controllers could be contacted.

    Common causes of this error include:

    - Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.

    - Domain controllers registered in DNS are not connected to the network or are not running.
    • Edited by Brian 49 Monday, December 11, 2017 5:16 PM Changed to correct DNS error
    Monday, December 11, 2017 2:59 PM

All replies

  • Windows IP Configuration

       Host Name . . . . . . . . . . . . : MKDC1
       Primary Dns Suffix  . . . . . . . : mk1
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : mk1

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server
     Adapter
       Physical Address. . . . . . . . . : 18-A9-05-46-2B-BC
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d94e:5343:a197:930d%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.0.200(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 172.16.0.254
       DHCPv6 IAID . . . . . . . . . . . : 219719941
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-31-B3-3A-18-A9-05-46-2B-BC

       DNS Servers . . . . . . . . . . . : ::1
                                           172.16.0.200
                                           172.16.0.206
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Monday, December 11, 2017 4:11 PM
  • Hi ,

    >>About a month ago I was not able to join the domain mk1.

    All PC or just one PC?

    Would you please post the result of running ipconfig/all at the command prompt on the client computer to let us know the machine’s configuration?

    If you are unable to add one computer to your domain, please check if the PC could ping DC.

    You might turn on exhaustive debugging mode of NSlookup, this will display detailed information of name resolving process.

    Open Command Prompt on client ,type nslookup and type set d2 .We could find out the problem through the process .
    >NSlookup
    >set d2
    >[name which you want to resolve]

    Please note:Any private information you share in a public forum might be seen or collected by other persons, please delete/black the private information before you post.

    Best Regards,

    Candy


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

    Tuesday, December 12, 2017 3:29 AM
  • Hi ,

    Just want to confirm the current situations.

    Best Regards,

    Candy


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

    Wednesday, December 13, 2017 8:55 AM
  • Default Server:  localhost
    Address:  ::1

    > set d2
    > mkdc1
    Server:  localhost
    Address:  ::1

    ------------
    SendRequest(), len 27
        HEADER:
            opcode = QUERY, id = 2, rcode = NOERROR
            header flags:  query, want recursion
            questions = 1,  answers = 0,  authority records = 0,  additional = 0

        QUESTIONS:
            mkdc1.mk1, type = A, class = IN

    ------------
    ------------
    Got answer (43 bytes):
        HEADER:
            opcode = QUERY, id = 2, rcode = NOERROR
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 1,  authority records = 0,  additional = 0

        QUESTIONS:
            mkdc1.mk1, type = A, class = IN
        ANSWERS:
        ->  mkdc1.mk1
            type = A, class = IN, dlen = 4
            internet address = 172.16.0.200
            ttl = 3600 (1 hour)

    ------------
    ------------
    SendRequest(), len 27
        HEADER:
            opcode = QUERY, id = 3, rcode = NOERROR
            header flags:  query, want recursion
            questions = 1,  answers = 0,  authority records = 0,  additional = 0

        QUESTIONS:
            mkdc1.mk1, type = AAAA, class = IN

    ------------
    ------------
    Got answer (103 bytes):
        HEADER:
            opcode = QUERY, id = 3, rcode = NOERROR
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0

        QUESTIONS:
            mkdc1.mk1, type = AAAA, class = IN
        AUTHORITY RECORDS:
        ->  mk1
            type = SOA, class = IN, dlen = 64
            ttl = 3600 (1 hour)
            primary name server = mkdc1.mk1
            responsible mail addr = hostmaster.mk1.***********.local
            serial  = 12999
            refresh = 900 (15 mins)
            retry   = 600 (10 mins)
            expire  = 86400 (1 day)
            default TTL = 3600 (1 hour)

    ------------
    Name:    mkdc1.mk1
    Address:  172.16.0.200

    _______________________________________________________

    Now I can join the domain if I do 

    ___________________________________________________

    In the registry of the client computer you are trying to join to the Single Label Domain add the following registry entry:<o:p></o:p>

    Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters<o:p></o:p>

    Create a REG_DWORD (32-Bit) Value called AllowSingleLabelDnsDomain<o:p></o:p>

    Change the Data Value of the newly created registry entry from 0 to 1<o:p></o:p>

    Reboot the computer and you will be able to join your remote computer to the Single Label Domain.

    ____________________________________________________________________________________

    Now I can join the domain when I do  the above. I never had to do this before it started about a month ago. 

    Wednesday, December 13, 2017 8:38 PM
  • Seems like my domain turned into a single level domain. I have no clue on how to fix it either. 
    Wednesday, December 13, 2017 8:39 PM
  • Hi ,

    sorry for the delayed response.

    Best-practice Active Directory domain names consist of one or more subdomains that are combined with a top-level domain that is separated by a dot character ("."). The following are some examples:
    contoso.com
    corp.contoso.com

    Single-label names consist of a single word like ""contoso."

    The domain name "MK1" is a single level domain.

    For your reference:

    Deployment and operation of Active Directory domains that are configured by using single-label DNS names

    https://support.microsoft.com/en-us/help/300684/deployment-and-operation-of-active-directory-domains-that-are-configur

    Best Regards,
    Candy


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

    Friday, December 15, 2017 8:31 AM
  • Hi ,

    Just checking in to see if the information provided was helpful.

    Please let us know if you would like further assistance.

    Best Regards,

    Candy


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

    Monday, December 18, 2017 9:06 AM
  • Hi ,

    Did you have any updates?

    Best Regards,

    Candy


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

    Thursday, December 21, 2017 9:16 AM