DNS problems

[Auddog]

I have a windows 2000 PDC server (sp4) that is running my DNS and Exchange.
The server has been pretty taxed as of late so I decided to add another
server to the system. I want my second server to be a DC as well as a
secondary DNS server. I installed the DNS server first and made it a
Standard secondary of the existing zone. Everything went smooth and the
zone appear to have replicated. I then promoted the server via dcpromo to
be an addition DC. It appears that this worked also(?). Both of the
servers I can ping via name and ip address. When I run netdiag /testNS on
the PDC, I get the follow error [FATAL] The DNS registration for the
servername.domain.com is incorrect on all DNS servers. I can see all the
net shares (SYSVOL, NETLOGON) on the PDC, but can not on the second server.
When I run dcdiag on the second server, I get an error under the frssysvol
saying: No record of File Replication System, SYSVOL, started.

I'm not sure where to go from here. Any help that you can provide would be
greatly appreciated.

A

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I have a windows 2000 PDC server (sp4) that is running my
DNS and Exchange. The server has been pretty taxed as of
late so I decided to add another server to the system. I
want my second server to be a DC as well as a secondary
DNS server. I installed the DNS server first and made it
a Standard secondary of the existing zone. Everything
went smooth and the zone appear to have replicated. I
then promoted the server via dcpromo to be an addition
DC. It appears that this worked also(?). Both of the
servers I can ping via name and ip address. When I run
netdiag /testNS on the PDC, I get the follow error
[FATAL] The DNS registration for the
servername.domain.com is incorrect on all DNS servers. I
can see all the net shares (SYSVOL, NETLOGON) on the PDC,
but can not on the second server. When I run dcdiag on
the second server, I get an error under the frssysvol
saying: No record of File Replication System, SYSVOL,
started.

I'm not sure where to go from here. Any help that you
can provide would be greatly appreciated.

A

Did you try dcdiag /fix and netdiag /fix?

 

[Auddog]

Yes, I have. It still doesn't get rid of the problems. I have now demoted
the second server and removed it as a secondary dns server. I've ran dcdiag
/fix on the server as well as netdiag /fix, but I'm still get the error
[FATAL] The DNS registration for the servername.domain.com is incorrect on
all DNS servers.

I'm fairly sure that this is causing my email server to be sparatic in
sending email as we are getting some of them back saying they are not
delivered in a timely fashion. Any help that you can provide will be
greatly appreciated.

A

In

I have a windows 2000 PDC server (sp4) that is running my
DNS and Exchange. The server has been pretty taxed as of
late so I decided to add another server to the system. I
want my second server to be a DC as well as a secondary
DNS server. I installed the DNS server first and made it
a Standard secondary of the existing zone. Everything
went smooth and the zone appear to have replicated. I
then promoted the server via dcpromo to be an addition
DC. It appears that this worked also(?). Both of the
servers I can ping via name and ip address. When I run
netdiag /testNS on the PDC, I get the follow error
[FATAL] The DNS registration for the
servername.domain.com is incorrect on all DNS servers. I
can see all the net shares (SYSVOL, NETLOGON) on the PDC,
but can not on the second server. When I run dcdiag on
the second server, I get an error under the frssysvol
saying: No record of File Replication System, SYSVOL,
started.

I'm not sure where to go from here. Any help that you
can provide would be greatly appreciated.

A

Did you try dcdiag /fix and netdiag /fix?

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Yes, I have. It still doesn't get rid of the problems.
I have now demoted the second server and removed it as a
secondary dns server. I've ran dcdiag /fix on the server
as well as netdiag /fix, but I'm still get the error
[FATAL] The DNS registration for the
servername.domain.com is incorrect on all DNS servers.

I'm fairly sure that this is causing my email server to
be sparatic in sending email as we are getting some of
them back saying they are not delivered in a timely
fashion. Any help that you can provide will be greatly
appreciated.

Next time, don't add the secondary zone, point the will be DC to the current
DC for DNS only. Run DCPROMO then the zone will replicate to the second DC
without any further action from you. Do not manually add the zone.
Once the zone has replicate then you can add the second DC's address for
DNS.

 

[Auddog]

I'm not sure I'm following. Should I have DNS installed prior to promoting
my second server? If yes, should I configure it? Also, should I have the
DNS under my lan adapter properties set to the PDC (192.168.100.100) for the
primary only and itself as secondary?

A

In

Yes, I have. It still doesn't get rid of the problems.
I have now demoted the second server and removed it as a
secondary dns server. I've ran dcdiag /fix on the server
as well as netdiag /fix, but I'm still get the error
[FATAL] The DNS registration for the
servername.domain.com is incorrect on all DNS servers.

I'm fairly sure that this is causing my email server to
be sparatic in sending email as we are getting some of
them back saying they are not delivered in a timely
fashion. Any help that you can provide will be greatly
appreciated.

Next time, don't add the secondary zone, point the will be DC to the
current
DC for DNS only. Run DCPROMO then the zone will replicate to the second DC
without any further action from you. Do not manually add the zone.
Once the zone has replicate then you can add the second DC's address for
DNS.

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I'm not sure I'm following. Should I have DNS installed
prior to promoting my second server? If yes, should I
configure it? Also, should I have the DNS under my lan
adapter properties set to the PDC (192.168.100.100) for
the primary only and itself as secondary?

You can and should have DNS installed, just no zones and don't use it in
TCP/IP properties, UNTIL the AD zone has replicated to it.
Do not let DCPromo configure DNS when running DCPROMO, it will create a
second conflicting zone in Active Directoy, which overwrites any existing
zone on Win2k and on Win2k3 it can create zone conflict that you have to
delete.

 

[Auddog]

After that is all done, should I make my second server a GC also?

A