|
Question : Windows 2003 server slow boot issue
|
|
We have an Windows 2k3 server that provides FSMO, DHCP and DNS for our domain. Since applying SP1, the server takes a long time to boot up (>15 minutes). This only happens when the DNS server IP address points at itself (TCP/IP Properties). If a secondary DNS server IP is added, the server boots up as expected.
The secondary DNS server on the domain also experiences this slow boot problem if the DNS server IP address points only to itself.
Only the two servers running DNS service have this slow boot problem. It appears when the servers start up, they can't access their own DNS service.
This isn't so much an issue as it is an pain, since everything work okay once the server comes up. It does cause a delay if we have to power all the servers on after a power outage, since both DNS servers are down at the same time.
Has anyone else run into this problem and more importantly, is there a fix?
|
Answer : Windows 2003 server slow boot issue
|
|
I recommend:
server1 dns1=instelf dns2=other dns serve
server2 dns1=server 1 IP dns2=itsself
|
|
|
|