missing dns records such as _msdcs and getting error 5781 on win2k dc

  • Thread starter Thread starter Marc I.
  • Start date Start date
M

Marc I.

hi,

users cannot join the domain due to dns issues.....the server is missing records such as _msdcs and getting eventID error 5781 on a win2k dc

how I populate DNS with all the required srv and _msdcs records since all there is now is one A record for the server


Marc
 
Marc said:
hi,

users cannot join the domain due to dns issues.....the server is missing
records such as _msdcs and getting eventID error 5781 on a win2k dc
how I populate DNS with all the required srv and _msdcs records since
all there is now is one A record for the server
Click to expand...

when You are saying server is missing entries in _msdcs zone You are
talking about DC as a server?
To register this records for DC just ensure thath DC in the TCP\IP
settings is pointing to good DNS server and restart netlogon service
 
This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX) couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck
 
If this DC is pointing to itself, ensure that the DNS zone is configured to
accept dynamic updates and ensure that the DHCP client service is running
and set to automatic (even though your DC isn't a DHCP client).

Then delete the _msdcs domain and restart netlogon.

Or you can run netdiag /fix

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX) couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck
 
I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing entries

ptwilliams said:
If this DC is pointing to itself, ensure that the DNS zone is configured
to
accept dynamic updates and ensure that the DHCP client service is running
and set to automatic (even though your DC isn't a DHCP client).

Then delete the _msdcs domain and restart netlogon.

Or you can run netdiag /fix

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX)
couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck
Click to expand...
 
Great news!!!

Did you create any of the sub-domains yourself? If so, this is not
recommended. However, if you did restart netlogon all should be well. In
the future restarting netlogon will suffice; if you create the A records
yourself, you may accidently add invalid entries, which could cause
problems. In future, let the DHCP service worry about it...

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing entries

ptwilliams said:
If this DC is pointing to itself, ensure that the DNS zone is configured
to
accept dynamic updates and ensure that the DHCP client service is running
and set to automatic (even though your DC isn't a DHCP client).

Then delete the _msdcs domain and restart netlogon.

Or you can run netdiag /fix

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX)
couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck
Click to expand...
 
restarting netlogon hadn't fixed the issue...I didnt add any entries just a
forward zone called _msdcs.domainname...then restarted netlogon

ptwilliams said:
Great news!!!

Did you create any of the sub-domains yourself? If so, this is not
recommended. However, if you did restart netlogon all should be well. In
the future restarting netlogon will suffice; if you create the A records
yourself, you may accidently add invalid entries, which could cause
problems. In future, let the DHCP service worry about it...

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing
entries
Click to expand...
 
If restarting netlogon didn't fix this, then you need to check that the DHCP
client service is running and is set to automatically start. If it is,
restarting is all you need to do. It can take a couple of minutes to take
effect.

netdiag /fix will also do this, but netlogon should. As it checks/ does
this every twelve hours.

Delete the _msdcs domain and restart netlogn. Go make a coffee and see what
happens. If it's not re-registering then we need to address this...

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

restarting netlogon hadn't fixed the issue...I didnt add any entries just a
forward zone called _msdcs.domainname...then restarted netlogon

ptwilliams said:
Great news!!!

Did you create any of the sub-domains yourself? If so, this is not
recommended. However, if you did restart netlogon all should be well. In
the future restarting netlogon will suffice; if you create the A records
yourself, you may accidently add invalid entries, which could cause
problems. In future, let the DHCP service worry about it...

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing
entries
Click to expand...
 
Back
Top