Windows 2003 Slow Startup - DNS

[Mike Jenkins]

I am currently testing an upgrade from an NT4 domain to 2K3 with AD. I
have taken a BDC from our current domain, promoted to PDC, upgraded to
2K3, then 2K3 installed AD and DNS for me. Once this was all working,
I added another DC, then installed another AD integrated DNS server
for my primary zone. DNS seems to replicate OK between the two server
and AD is functioning correctly.

If the DNS server entry in the TCP/IP config for each server points at
itself, the server will take up to 10 minutes with Preparing Network
Connections... on the screen to start up with various DNS/AD errors in
the event log. When it has started, netdiag /test:dns will report that
the server is not registered in DNS. Looking at the event viewer, it
seems that the DNS service does not start until immediately before the
login window appears.

I changed the DNS entries on each machine to point to the other for
primary DNS, and as long as the other machine is started, this will
give an error-free and fast bootup. It seems that 2K3 is trying to
start AD services before DNS is initialised.

However, the long-startup problem seems random, and it didn't happen
before I added the second DC.

Questions are:

1. Is my current setup (primary DNS set to the other DC) desirable? Is
it likely to cause problems?

2. Is the slow-startup problem normal for multi-DC environments?

Thanks in advance for any advice.

 

[Kevin D. Goodknecht Sr. [MVP]]

I am currently testing an upgrade from an NT4 domain to 2K3 with AD. I
have taken a BDC from our current domain, promoted to PDC, upgraded to
2K3, then 2K3 installed AD and DNS for me. Once this was all working,
I added another DC, then installed another AD integrated DNS server
for my primary zone. DNS seems to replicate OK between the two server
and AD is functioning correctly.

If the DNS server entry in the TCP/IP config for each server points at
itself, the server will take up to 10 minutes with Preparing Network
Connections... on the screen to start up with various DNS/AD errors in
the event log. When it has started, netdiag /test:dns will report that
the server is not registered in DNS. Looking at the event viewer, it
seems that the DNS service does not start until immediately before the
login window appears.

Run this: netdiag /fix

I changed the DNS entries on each machine to point to the other for
primary DNS, and as long as the other machine is started, this will
give an error-free and fast bootup. It seems that 2K3 is trying to
start AD services before DNS is initialised.

However, the long-startup problem seems random, and it didn't happen
before I added the second DC.

Questions are:

1. Is my current setup (primary DNS set to the other DC) desirable? Is
it likely to cause problems?

Both DCs should use the other DC and itself for DNS.

2. Is the slow-startup problem normal for multi-DC environments?

This is common for any DC that uses only istelf for DNS when using AD
integrated zones.
DNS can't load the AD zone until AD starts on the DC and AD will wait for
DNS to start. It is a catch 22 situation don't you see?

 

[Mike Jenkins]

Run this: netdiag /fix

Everything passes there.

Both DCs should use the other DC and itself for DNS.

I've set this now and all is fine if the other DNS server is online
when starting up.

This is common for any DC that uses only istelf for DNS when using AD
integrated zones.
DNS can't load the AD zone until AD starts on the DC and AD will wait for
DNS to start. It is a catch 22 situation don't you see?

Yes, that makes sense. It's pretty obvious I suppose, thanks for the
input.