SRV error joining Active Directory

Larry Marshall 21 Reputation points
2021-08-30T17:22:20.013+00:00

I am running AD 2008, which had been working until a few days ago. Suddenly some workstations cannot find resources.

I removed a single workstation and attempted to re-join, which displayed the following.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Dire

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.domain.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

192.168.1.9

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

domain.com
com
. (the root zone)

This makes no sense to me given the following response from nslookup on the DC (192.168.1.9) itself.

C:\Users\Administrator>nslookup
Default Server: fileserver.domain.com
Address: 192.168.1.18

> set type=all
> _ldap._tcp.dc._msdcs.domain.COM
Server: fileserver.domain.com
Address: 192.168.1.18

_ldap._tcp.dc._msdcs.domain.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = domaindc.domain.com
_ldap._tcp.dc._msdcs.domain.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = fileserver.domain.com
domaindc.domain.com internet address = 192.168.1.9
fileserver.domain.com internet address = 192.168.1.18
> EXIT
Server: fileserver.domain.com
Address: 192.168.1.18

Any ideas on where to start?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,094 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426.3K Reputation points MVP
    2021-08-30T19:00:17.25+00:00

    On FILESERVER add the server's own static ip address (192.168.1.18) listed for DNS, then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

    On POWELLDC add the server's own static ip address (192.168.1.9) listed for DNS, then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

    • DFSR on POWELLDC, current value DISABLED, expected value AUTO_START (change it to automatic)
    • w32time Service is stopped on [POWELLDC] (I'd check the system event log for related errors, needs to run)
    • NETLOGON Service is stopped on [POWELLDC] (I'd check the system event log for related errors, needs to run)
    • Invalid service startup type: w32time on FILESERVER, current value DEMAND_START, expected value AUTO_START (change it to automatic)

    On DESKTOP-K7SK4TG remove the public DNS (8.8.8.8) then do ipconfig /flushdns, ipconfig /registerdns

    there may also be a rouge IPv6 DHCP server (router?) on the network that if not configured can cause problems. Turn of the function if not configured

    If problems persist after corrections then put up a new set of files to look at.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Dave Patrick 426.3K Reputation points MVP
    2021-08-30T17:39:48.983+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.


  2. Lars Zeb 1 Reputation point
    2021-08-30T18:41:50.397+00:00
    0 comments No comments

  3. Lars Zeb 1 Reputation point
    2021-08-30T19:44:26.3+00:00

    I do not think there is a rogue DHCP router.

    OneDrive

    I hope I followed your instructions accurately.

    Thanks for your help.

    0 comments No comments

  4. Dave Patrick 426.3K Reputation points MVP
    2021-08-30T19:51:25.477+00:00

    DFS Replication service has detected an NTFS change journal wrap. DFS Replication service was not running on this computer for an extended period of time. The DFS Replication service could not keep up with the rate of file changes on the volume. The service has automatically initiated the journal wrap recovery process.

    Hopefully it will recover. If not the simplest solution may be to move the roles off, demote, reboot, promo it again.

    --please don't forget to upvote and Accept as answer if the reply is helpful--