Installing AD and the DNS not properly configured.

  • Thread starter Thread starter James MacKenzie
  • Start date Start date
J

James MacKenzie

I have installed AD probably 100 times in the past 6 months. I have run
numerous tests on it and have never ever seen this before. The situation is
this

I installed Win2K Server on a new server. Applied SP4 and all the other
critical and recommended updates (most of the recommended ones). The server
was a new server on a new network with 7 clients all running WinXP Pro -
currently in a workgroup as there was no server. I ran dcpromo and added a
new domain forest, tree etc. The dns name was RAR.local. NetBios was RAR and
as there was no detectable dns it asked to install which I did. I also set
permissions to be win2K only. The promotion worked without errors and I
rebooted and logged in. I always do a quick check on the dns after a
promotion - not that it has never not worked - but I know how important it
is so I always check. This time, there was no root and the rar.local zone
had only 2 entries. I have never before seen this when installing dns as
part of the DCPromo. If the dns is added before or after the dc promo, you
have to add the zone manually and then it can take a few mins before it is
populated from AD.

I waited for 20 mins, then restarted. Still the dns was not properly
populated. I tried to remove it and add it back. I checked in AD under the
Microsoftdns and there were only the 2 entries there so obviously the dns
could not be populated.

I tired to demote, add back dns and re-promote - restarting between each
thing to be safe, and still nothing. I tried installing 2K Server on a
workstation that I have tested it on before - same make and model at
least - and the same thing happened.

The next day in a completely separate office, I ran tests on the same
hardware - the workstation, and it worked without a hitch. I tried with
Win2K only and then with various stages of updates till I had all updates.
Still it worked without a hitch. I also tried using the exact same domain
name.

In summary, I have installed 2K Server with AD at least 100 times in the
past 6 months. I have tested every combination of installing the dns as part
of dc promo, adding it later, adding it before and having it on a different
server. If dns is installed as part of dcpromo it is because it cannot
detect a suitable dns server on the network and it always installs it as a
root server. Again, the root is easily removed after successful
installation. I have never ever had a problem.

As far as I can see, in the original office it was installed on a new server
and a workstation for testing. Both suffered the same fate. There was no way
to get AD to populate itself with the correct domain dns records. In another
unconnected office, no problems were encountered installing on and identical
workstation. The only difference I can see is the actual physical location.
Each system was connected to a single switch (identical switches) and the
switch was not connected to anything else except a DSL fixed ip address
broadband connection. Each DC had a fixed IP, subnet and gateway set and had
its NIC dns set to itself before promotion.

Does anyone have any ideas here. I am pulling my hair out.

Thanks
 
-----Original Message-----
I have installed AD probably 100 times in the past 6 months. I have run
numerous tests on it and have never ever seen this before. The situation is
this

I installed Win2K Server on a new server. Applied SP4 and all the other
critical and recommended updates (most of the recommended ones). The server
was a new server on a new network with 7 clients all running WinXP Pro -
currently in a workgroup as there was no server. I ran dcpromo and added a
new domain forest, tree etc. The dns name was RAR.local. NetBios was RAR and
as there was no detectable dns it asked to install which I did. I also set
permissions to be win2K only. The promotion worked without errors and I
rebooted and logged in. I always do a quick check on the dns after a
promotion - not that it has never not worked - but I know how important it
is so I always check. This time, there was no root and the rar.local zone
had only 2 entries. I have never before seen this when installing dns as
part of the DCPromo. If the dns is added before or after the dc promo, you
have to add the zone manually and then it can take a few mins before it is
populated from AD.

I waited for 20 mins, then restarted. Still the dns was not properly
populated. I tried to remove it and add it back. I checked in AD under the
Microsoftdns and there were only the 2 entries there so obviously the dns
could not be populated.

I tired to demote, add back dns and re-promote - restarting between each
thing to be safe, and still nothing. I tried installing 2K Server on a
workstation that I have tested it on before - same make and model at
least - and the same thing happened.

The next day in a completely separate office, I ran tests on the same
hardware - the workstation, and it worked without a hitch. I tried with
Win2K only and then with various stages of updates till I had all updates.
Still it worked without a hitch. I also tried using the exact same domain
name.

In summary, I have installed 2K Server with AD at least 100 times in the
past 6 months. I have tested every combination of installing the dns as part
of dc promo, adding it later, adding it before and having it on a different
server. If dns is installed as part of dcpromo it is because it cannot
detect a suitable dns server on the network and it always installs it as a
root server. Again, the root is easily removed after successful
installation. I have never ever had a problem.

As far as I can see, in the original office it was installed on a new server
and a workstation for testing. Both suffered the same fate. There was no way
to get AD to populate itself with the correct domain dns records. In another
unconnected office, no problems were encountered installing on and identical
workstation. The only difference I can see is the actual physical location.
Each system was connected to a single switch (identical switches) and the
switch was not connected to anything else except a DSL fixed ip address
broadband connection. Each DC had a fixed IP, subnet and gateway set and had
its NIC dns set to itself before promotion.

Does anyone have any ideas here. I am pulling my hair out.

Thanks


.
Click to expand...
James,

There are a couple of things that you can do. I usually
would try the "ipconfig /registerdns" command line
command. If that does not work then I might try "net
stop netlogon", then "ipconfig /registerdns" and
finally "net start netlogon".

Another way to do it ( and a favorite of mine ) is to
install the Support Tools on each and every server you
have. The Support Tools can be found on the WIN2000
Server CD or - even better - on the WIN2000 Service Pack
CD. They are located in the Support | Tools folder.

Once you have installed the Support Tools go to a command
prompt and run "netdiag /fix". This will often take care
of any "easy" fixes.

In the DNS Forward Lookup Zone did you have the four sub-
folders. Were they populated as they should be? I think
not, right?

After running either of these steps they should be
there. You can also run a DCDIAG /V and a NETDIAG /V
from the dommand prompt. This will give us a much better
idea of what is going on.

Also, I usually set up a Reverse Look Up Zone in DNS. I
also set up Active Directory Sites and Services
immediately. This is where you create a Site ( should be
there already ), then create subnet(s) and associate the
subnet(s) with the appropriate Site.

Oh, and just to make sure - your DNS was set as Active
Directory Integrated and "allow secure updates only",
right? When troubleshooting DNS we might want to set
that to "yes" instead....

HTH,

Cary
 
Back
Top