I've never had to do this but here is an article that details how to delay
the netlogon service until DNS is up and running.
See:
http://support.microsoft.com/kb/193888/en-us


hth

"altria" <urbantec92@msn.com> wrote in message
news:uRs424yaHHA.2436@TK2MSFTNGP06.phx.gbl...
> Hello Danny and thanks for the quick response!
>
> Actually the DNS server resides on the machines itself with the IP address
> of the box in question. the configuration is not the issue. It was
> something that I read that was innate in Windows 2003. I just forgot where
> I seen this from. Anyway, i am suppose to change the dependency order for
> services that startup but I wanted to make sure that I changed the exact
> ones, thus the documentation I am looking for is needed.
>
> Thanks,
> Altria
>
> --
> "Danny Sanders" <DSanders@NOSPAMciber.com> wrote in message
> news:euel1ZyaHHA.4616@TK2MSFTNGP03.phx.gbl...
>>> Upon restarting my win2k3 (DC) server, I usually get a long delay to
>>> logon or DNS service fails. Finally when I am able to login, I notice
>>> under event viewer that the DNS cannot locate AD.
>>
>> Sounds like the DNS server this server is pointing to in the properties
>> of TCP/IP (for DNS) is not up and running during the reboot of this
>> server. Provide it with a DNS server that is up during the reboot.
>>
>>
>> hth
>> DDS
>>
>> "altria" <urbantec92@msn.com> wrote in message
>> news:uwcHrWyaHHA.2088@TK2MSFTNGP05.phx.gbl...
>>> Hello All,
>>> I have a question that pertains to a topic I came across some time ago.
>>>
>>> Upon restarting my win2k3 (DC) server, I usually get a long delay to
>>> logon or DNS service fails. Finally when I am able to login, I notice
>>> under event viewer that the DNS cannot locate AD.
>>>
>>> I remember reading an article that can prevent this by making DNS
>>> service depend upon DS upon restart (or vice versa, my memory is failing
>>> me at the moment!). Anyone can point me to the documentation regarding
>>> this?
>>>
>>> TIA,
>>> Altria
>>>
>>>
>>>
>>
>>
>
>