DCPROMO

  • Thread starter Thread starter bill s via WinServerKB.com
  • Start date Start date
B

bill s via WinServerKB.com

Are there negative ramifications demoting a sole DC to member and then back
to DC again?
I am trying to set up a network but am struggling with DNS....doesn't seem to
load the same way twice.
 
You can demote and promote as long as you understand you will lose ALL AD
objects (Users, groups, etc...) and any machines that are currently joined
to the domain will have to be re-joined.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
 
bill s via WinServerKB.com wrote :
Are there negative ramifications demoting a sole DC to member and then back
to DC again?
I am trying to set up a network but am struggling with DNS....doesn't seem to
load the same way twice.
Click to expand...

to "refresh" your dns zone you could simply delete the zone
restart your DC and the DNS zone will be recreated

you don't have to dcpromo anything for that

grtz
 
bill said:
Are there negative ramifications demoting
a sole DC to member and then back to DC again?
I am trying to set up a network but am struggling
with DNS....doesn't seem to load the same way twice.
Click to expand...
On the face of it, that doesn't seem like a good
solution to a DNS problem. A bit like smashing a walnut
with a sledgehammer Do you care to submit a post with
details of what problems you are seeing?

Cheers,

Cliff
 
Enkidu said:
On the face of it, that doesn't seem like a good
solution to a DNS problem. A bit like smashing a walnut
with a sledgehammer Do you care to submit a post with
details of what problems you are seeing?

Cheers,

Cliff
Click to expand...
yes it is overkill.....but good practice.....being on a practice domain.
I keep getting 'cannot find domain name" as an error when trying to join a
PC to the DC. This is after I get the window that requires a valid name and
password that can join.
I know AD sets up DNS because it needs it and it's how it resolves names to
IP address but I don't think it is setting up right. There never seems to be
an "A" file in my forward zone. Now, I am not looking to host DNS so should
there be anything in my reverse zone? Is not the "A" file an address file for
the server??

The first time I tried this it worked and I did nothing different than I am
now. Unfortunately the DC was set up on an older computer and the drive
crashed before it really got into service for long.

Somewhere DNS is not setting right....
Any help would be great.thanks
 
bill said:
yes it is overkill.....but good practice.....being on
a practice domain. I keep getting 'cannot find domain
name" as an error when trying to join a PC to the DC.
This is after I get the window that requires a valid
name and password that can join.

I know AD sets up DNS because it needs it and it's
how it resolves names to IP address but I don't think
it is setting up right. There never seems to be an "A"
file in my forward zone. Now, I am not looking to host
DNS so should there be anything in my reverse zone? Is
not the "A" file an address file for the server??

The first time I tried this it worked and I did nothing
different than I am now. Unfortunately the DC was set
up on an older computer and the drive crashed before it
really got into service for long.

Somewhere DNS is not setting right....
Any help would be great.thanks
Click to expand...
How is the DNS set in the NICs on the client and on the server?

Cheers,

Cliff
 
Enkidu said:
[quoted text clipped - 26 lines]
Somewhere DNS is not setting right....
Any help would be great.thanks
Click to expand...

How is the DNS set in the NICs on the client and on the server?

Cheers,

Cliff
Cliff....the clients point to the server address.
Click to expand...
 
Back
Top