Problem DNS, Windows is slow to start at bootup

  • Thread starter Thread starter antonin
  • Start date Start date
A

antonin

Hi,

I have recently installed a new Primary Windows server.
After rebooting, Windows took 25-30 minutes to boot. He
hangs on network connection. I've restarted the server and
booted in safe mode, I putted the DNS service manual and I
was able to logon to my server. I have read many articles
but I have the problem yet.

Thanks

Antonin
 
The hanging at that point in booting is almost always due to dns name
resolution, or lack there of.
When you say "primary windows server" I assume you mean a domain controller.
During the promotion process, if dns was not already installed, it would
have complained about not being able to resolve your domain name and ask if
you want to have it install/configure dns, which normally folks should do.
Not sure at what point, or how, dns got installed, but first thing; If this
machine is running sp4 be sure that you do not have a single label dns
domain name (ie, no com, net, org, local etc after the name);
300684 Information About Configuring Windows 2000 for Domains With
Single-Label
http://support.microsoft.com/?id=300684

If that's ok, then be sure you have your 4 folders starting with "_" under
the forward lookup dns zone for your domain. This is probably where the
problem is if not single label as above.
Be sure the dc is pointed to only itself for dns in ip properties(other
config possible with dns but keeping things simple here), and if there are
other addresses there, remove them and run "ipconfig /flushdns" to clear
cache.
Be sure when you do properties of your domain zone in dns that it will
accept dynamic updates (depending on zone type - either Yes or Allow Secure
Only is ok)
The SRV records in those 4 folders are rebuilt every time the machine is
either rebooted or the netlogon service is re-started so do either (suggest
the netlogon service to avoid reboot in case it still isnt' right) and see
if those registrations are there.
You should be able to ping your dns domain name (xyz.com etc) and get a
reply as well as your machinename.domainname if things are working like they
should.


--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
In
David Brandt said:
The hanging at that point in booting is almost always due to dns name
resolution, or lack there of.
When you say "primary windows server" I assume you mean a domain
controller. During the promotion process, if dns was not already
installed, it would have complained about not being able to resolve
your domain name and ask if you want to have it install/configure
dns, which normally folks should do. Not sure at what point, or how,
dns got installed, but first thing; If this machine is running sp4
be sure that you do not have a single label dns domain name (ie, no
com, net, org, local etc after the name); 300684 Information About
Configuring Windows 2000 for Domains With Single-Label
http://support.microsoft.com/?id=300684

If that's ok, then be sure you have your 4 folders starting with "_"
under the forward lookup dns zone for your domain. This is probably
where the problem is if not single label as above.
Be sure the dc is pointed to only itself for dns in ip
properties(other config possible with dns but keeping things simple
here), and if there are other addresses there, remove them and run
"ipconfig /flushdns" to clear cache.
Be sure when you do properties of your domain zone in dns that it will
accept dynamic updates (depending on zone type - either Yes or Allow
Secure Only is ok)
The SRV records in those 4 folders are rebuilt every time the machine
is either rebooted or the netlogon service is re-started so do either
(suggest the netlogon service to avoid reboot in case it still isnt'
right) and see if those registrations are there.
You should be able to ping your dns domain name (xyz.com etc) and get
a reply as well as your machinename.domainname if things are working
like they should.
Click to expand...

Hi David,

Well put.
:-)


In addition, Here's another link that may help in answering some questions
for Antonin as to why AD needs the internal DNS only:

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003
DNS
http://support.microsoft.com/?id=291382


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
Hi,

I have recently installed a new Primary Windows server.
After rebooting, Windows took 25-30 minutes to boot. He
hangs on network connection. I've restarted the server and
booted in safe mode, I putted the DNS service manual and I
was able to logon to my server. I have read many articles
but I have the problem yet.

Thanks

Antonin
.
hi antonin
Click to expand...

i am currently experincing a similiar problem the reason
that your server takes so long to boot is because its
looking to your isp to resolve the addresses, you need to
put in the local dns addresses to resolve the network
names .
 
how did u solved that?

i am currently experincing a similiar problem the reason
that your server takes so long to boot is because its
looking to your isp to resolve the addresses, you need to
put in the local dns addresses to resolve the network
names .
Click to expand...
 
Back
Top