DNS Issue

  • Thread starter Thread starter paul carruthers
  • Start date Start date
P

paul carruthers

I have a domain. Its called "Domain" - please note the lack of .com
etc

I have two servers. PDC and BDC. Both running Win2k Server with Sp4
installed.

PDC ( 192.168.1.12 ) has DNS running for a domain called "Domain". I
have it running in Active Directory mode - with all updates allowed.
Reverse dns is the same.

However NTFRS is failing to sycn PDC and BDC. Running dcdiag /fix
points the finger straight at the DNS ( See below ). I have setup a
registry key on both PDC & BDC due to my domain name
"UpdateTopLevelDomainZones" = 0x1 to
"HKLM\System\CurrentControlSet\Services\DnsCache\Parameters"

I found this on eventid.com

Any ideas ?

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\pdc
Starting test: Connectivity
......................... pdc passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\pdc
Starting test: Replications
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Schema,CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.14.
1337 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[bdc] DsBind() failed with error 1722,
The RPC server is unavailable..
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.13.
1339 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:43.43.
The last success occurred at 2004-03-04 17:25.56.
1341 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
......................... pdc passed test Replications
Starting test: NCSecDesc
......................... pdc passed test NCSecDesc
Starting test: NetLogons
......................... pdc passed test NetLogons
Starting test: Advertising
Warning: pdc is not advertising as a time server.
......................... pdc failed test Advertising
Starting test: KnowsOfRoleHolders
......................... pdc passed test KnowsOfRoleHolders
Starting test: RidManager
......................... pdc passed test RidManager
Starting test: MachineAccount
......................... pdc passed test MachineAccount
Starting test: Services
w32time Service is stopped on [pdc]
Could not open IISADMIN Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
Could not open SMTPSVC Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
......................... pdc failed test Services
Starting test: ObjectsReplicated
......................... pdc passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... pdc passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 03/18/2004 12:31:34
Event String: The Directory Service consistency checker
has

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

......................... pdc failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

......................... pdc failed test systemlog

Running enterprise tests on : domain
Starting test: Intersite
......................... domain 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 1355
A Good Time Server could not be located.
......................... domain failed test FsmoCheck
I have a domain. Its called "Domain" - please note the lack of .com
etc

I have two servers. PDC and BDC. Both running Win2k Server with Sp4
installed.

PDC ( 192.168.1.12 ) has DNS running for a domain called "Domain". I
have it running in Active Directory mode - with all updates allowed.
Reverse dns is the same.

However NTFRS is failing to sycn PDC and BDC. Running dcdiag /fix
points the finger straight at the DNS ( I have attached only bits of
the result from dcdiag )

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\PDC
Starting test: Connectivity
......................... pdc passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\pdc
Starting test: Replications
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Schema,CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.14.
1337 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[bdc] DsBind() failed with error 1722,
The RPC server is unavailable..
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.13.
1339 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:43.43.
The last success occurred at 2004-03-04 17:25.56.
1341 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.

......................... pdc passed test Replications
Starting test: NCSecDesc
......................... pdc passed test NCSecDesc
Starting test: NetLogons
......................... pdc passed test NetLogons
Starting test: Advertising
Warning: pdc is not advertising as a time server.
......................... pdc failed test Advertising
Starting test: KnowsOfRoleHolders
......................... pdc passed test KnowsOfRoleHolders
Starting test: RidManager
......................... pdc passed test RidManager
Starting test: MachineAccount
......................... pdc passed test MachineAccount
Starting test: Services
w32time Service is stopped on [pdc]
Could not open IISADMIN Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
Could not open SMTPSVC Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
......................... pdc failed test Services
Starting test: ObjectsReplicated
......................... pdc passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... pdc passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 03/18/2004 12:31:34
Event String: The Directory Service consistency checker
has

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

......................... pdc failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

......................... pdc failed test systemlog

Running enterprise tests on : domain
Starting test: Intersite
......................... domain 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 1355
A Good Time Server could not be located.
......................... domain failed test FsmoCheck
 
As your domain name does not have a suffix you should follow the extra
configuration steps in this article.
http://support.microsoft.com/?id=300684

paul carruthers said:
I have a domain. Its called "Domain" - please note the lack of .com
etc

I have two servers. PDC and BDC. Both running Win2k Server with Sp4
installed.

PDC ( 192.168.1.12 ) has DNS running for a domain called "Domain". I
have it running in Active Directory mode - with all updates allowed.
Reverse dns is the same.

However NTFRS is failing to sycn PDC and BDC. Running dcdiag /fix
points the finger straight at the DNS ( See below ). I have setup a
registry key on both PDC & BDC due to my domain name
"UpdateTopLevelDomainZones" = 0x1 to
"HKLM\System\CurrentControlSet\Services\DnsCache\Parameters"

I found this on eventid.com

Any ideas ?

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\pdc
Starting test: Connectivity
......................... pdc passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\pdc
Starting test: Replications
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Schema,CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.14.
1337 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[bdc] DsBind() failed with error 1722,
The RPC server is unavailable..
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.13.
1339 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:43.43.
The last success occurred at 2004-03-04 17:25.56.
1341 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
......................... pdc passed test Replications
Starting test: NCSecDesc
......................... pdc passed test NCSecDesc
Starting test: NetLogons
......................... pdc passed test NetLogons
Starting test: Advertising
Warning: pdc is not advertising as a time server.
......................... pdc failed test Advertising
Starting test: KnowsOfRoleHolders
......................... pdc passed test KnowsOfRoleHolders
Starting test: RidManager
......................... pdc passed test RidManager
Starting test: MachineAccount
......................... pdc passed test MachineAccount
Starting test: Services
w32time Service is stopped on [pdc]
Could not open IISADMIN Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
Could not open SMTPSVC Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
......................... pdc failed test Services
Starting test: ObjectsReplicated
......................... pdc passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... pdc passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 03/18/2004 12:31:34
Event String: The Directory Service consistency checker
has

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

......................... pdc failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

......................... pdc failed test systemlog

Running enterprise tests on : domain
Starting test: Intersite
......................... domain 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 1355
A Good Time Server could not be located.
......................... domain failed test FsmoCheck
I have a domain. Its called "Domain" - please note the lack of .com
etc

I have two servers. PDC and BDC. Both running Win2k Server with Sp4
installed.

PDC ( 192.168.1.12 ) has DNS running for a domain called "Domain". I
have it running in Active Directory mode - with all updates allowed.
Reverse dns is the same.

However NTFRS is failing to sycn PDC and BDC. Running dcdiag /fix
points the finger straight at the DNS ( I have attached only bits of
the result from dcdiag )

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\PDC
Starting test: Connectivity
......................... pdc passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\pdc
Starting test: Replications
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Schema,CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.14.
1337 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[bdc] DsBind() failed with error 1722,
The RPC server is unavailable..
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: CN=Configuration,DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:41.36.
The last success occurred at 2004-03-04 17:19.13.
1339 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.
[Replications Check,pdc] A recent replication attempt failed:
From bdc to pdc
Naming Context: DC=domain
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS
lookup failure.
The failure occurred at 2004-03-18 12:43.43.
The last success occurred at 2004-03-04 17:25.56.
1341 failures have occurred since the last success.
The guid-based DNS name
1f6eaf85-e667-44b4-8ffd-01d3517f65a9._msdcs.domain
is not registered on one or more DNS servers.

......................... pdc passed test Replications
Starting test: NCSecDesc
......................... pdc passed test NCSecDesc
Starting test: NetLogons
......................... pdc passed test NetLogons
Starting test: Advertising
Warning: pdc is not advertising as a time server.
......................... pdc failed test Advertising
Starting test: KnowsOfRoleHolders
......................... pdc passed test KnowsOfRoleHolders
Starting test: RidManager
......................... pdc passed test RidManager
Starting test: MachineAccount
......................... pdc passed test MachineAccount
Starting test: Services
w32time Service is stopped on [pdc]
Could not open IISADMIN Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
Could not open SMTPSVC Service on [pdc]:failed with 1060:
The specified service does not exist as an installed service.
......................... pdc failed test Services
Starting test: ObjectsReplicated
......................... pdc passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... pdc passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 03/18/2004 12:31:34
Event String: The Directory Service consistency checker
has

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

An Warning Event occured. EventID: 0x800004F1
Time Generated: 03/18/2004 12:31:34
Event String: The attempt to establish a replication link
with

......................... pdc failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

An Error Event occured. EventID: 0x800009CF
Time Generated: 03/18/2004 12:26:35
Event String: The server service was unable to recreate
the

......................... pdc failed test systemlog

Running enterprise tests on : domain
Starting test: Intersite
......................... domain 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 1355
A Good Time Server could not be located.
......................... domain failed test FsmoCheck
Click to expand...
 
Thanks Simon,

Unfortuantely thats exactly what I have already applied to my DC's.

Both have since been rebooted but I still get the same event logged.
dcdiag /fix reports the guid based dns name isnt registered.

As part of a debug I have stripped both DC's to use just the one DNS
server. I have deleted and recreated its zone.

What I do find interesting is :
C:\Documents and Settings\Administrator>ipconfig /registerdns

Windows 2000 IP Configuration

Error: The system cannot find the file specified.
: Refreshing DNS names

Now - I was expecting a error but not that sort of error. MS knowledge
base 266319 reports you need to start the dhcp client - although I
am using a static ip. Re running the ipconfig I know get :

"Registration of the DNS resource records for all adapters of this
computer has b
een initiated. Any errors will be reported in the Event Viewer in 15
minutes."


This has resolved the issue on one main DC - so I am winning !

P
 
Back
Top