Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier)
-
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
This is what DHCP is for. In a typical environment you have to update almost nothing when replacing a DC.
To expand upon this, use DHCP reservations on almost anything, printers, servers, switches (if able), etc.
Use static IPs on:
DNS servers
DHCP servers
Firewalls
AD servers
VM hosts -
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
This is what DHCP is for. In a typical environment you have to update almost nothing when replacing a DC.
So would you typically put your servers on DHCP reservation? Also, I thought you once told me about the very thing I am asking about in my OP.. I just forgot the details
-
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
This is what DHCP is for. In a typical environment you have to update almost nothing when replacing a DC.
So would you typically put your servers on DHCP reservation? Also, I thought you once told me about the very thing I am asking about in my OP.. I just forgot the details
Typically, yes, DHCP Reservations are ideal. The power of static but with central control. I'm fine with static when they make sense, but DHCP gives you a lot of important flexibility.
-
@dashrender said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
Use static IPs on:
DNS servers
DHCP servers
AD serversThese are typically all on one server (or one per site) SO not as many servers as it sounds like.
Also random AD file servers are all DHCP reservations , not static. Just because it has a role, does not mean it is an AD server that needs a static IP.
-
Seriously, very little of anything needs to be a static IP.
Almost everything works on DNS. Even SQL servers. No one has an app that connects to SQL by IP. They use DNS names.
-
@jaredbusch said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
Seriously, very little of anything needs to be a static IP.
Almost everything works on DNS. Even SQL servers. No one has an app that connects to SQL by IP. They use DNS names.
Basically, in a normal network, you can have your default gateway be static and nothing else.
-
So basically, what I should do, is swap as much of my manual static to DHCP reservation that I possibly can. Then I can update DNS in the DHCP scope and all should be well... sounds like a good plan.
-
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
So basically, what I should do, is swap as much of my manual static to DHCP reservation that I possibly can. Then I can update DNS in the DHCP scope and all should be well... sounds like a good plan.
Correct. This will make things easier and easier over time.
-
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
-
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
I assume you have a Windows 2012 R2 or newer AD serve rthat is your DHCP server? If so, you can make a secondary.
If not, with any version back even to Server 2003, you can export your scope and reimport it on a new server.
-
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
DHCP Reservations are like normal DHCP Leases, so if you have them for, say 48 hours, you will likely have quite some time before things start to lose their leases. You have several choices...
- Have failover DHCP so that you are not dependent on a single once.
- Recreate everything by hand, for even 100 machines, this is trivial amounts of work as long as you document it.
- Take a backup and restore.
- Set the reservations programtically like through a script or state system.
-
@jaredbusch said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
I assume you have a Windows 2012 R2 or newer AD serve rthat is your DHCP server? If so, you can make a secondary.
If not, with any version back even to Server 2003, you can export your scope and reimport it on a new server.
2008 R2. But, what I will probably do is set up the new 2016 DC and then move DHCP role to that and set up the reservations and things. Then, when the time is right, I will point everything from old DC to new DC
-
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
DHCP Reservations are like normal DHCP Leases, so if you have them for, say 48 hours, you will likely have quite some time before things start to lose their leases. You have several choices...
- Have failover DHCP so that you are not dependent on a single once.
- Recreate everything by hand, for even 100 machines, this is trivial amounts of work as long as you document it.
- Take a backup and restore.
- Set the reservations programtically like through a script or state system.
nice, thanks!
-
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@jaredbusch said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
I assume you have a Windows 2012 R2 or newer AD serve rthat is your DHCP server? If so, you can make a secondary.
If not, with any version back even to Server 2003, you can export your scope and reimport it on a new server.
2008 R2. But, what I will probably do is set up the new 2016 DC and then move DHCP role to that and set up the reservations and things. Then, when the time is right, I will point everything from old DC to new DC
Don't forget those 2016 CALs (inside joke for those that saw the guy freak out about having to get CALs when updating Windows today.)
-
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
- Have failover DHCP so that you are not dependent on a single once.
Until he moves to 2016 he cannot have it "automagic" inside Windows Server. But he can manually have a backup made.
-
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@jaredbusch said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One last question... and I plan to look into reservation tomorrow.. but what happens with the reservations in the event that the DHCP server goes down and, say, is un-recoverable? I mean, sure it would be trivial to fire up a new server, but you'd still have all the reservations to rebuild, unless they were exported as backup and then you could import or something.. and this is worst-case. DHCP would probably never go down, except for that one time....
I assume you have a Windows 2012 R2 or newer AD serve rthat is your DHCP server? If so, you can make a secondary.
If not, with any version back even to Server 2003, you can export your scope and reimport it on a new server.
2008 R2. But, what I will probably do is set up the new 2016 DC and then move DHCP role to that and set up the reservations and things. Then, when the time is right, I will point everything from old DC to new DC
Don't forget those 2016 CALs (inside joke for those that saw the guy freak out about having to get CALs when updating Windows today.)
Oh for sure. I already have them set up in our budget (thanks to help I got from you guys on here)
-
@scottalanmiller said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
DHCP Reservations are like normal DHCP Leases, so if you have them for, say 48 hours, you will likely have quite some time before things start to lose their leases. You have several choices...
I typically set my lease time to 8 hours. I want things to break during the business day whenever possible.
Machines should renew ever 4 hours with that setting. So if shit hits the fan, someone should fail to renew before you go home and clue you in to an issue. -
@dave247 said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
I was wondering, is there an easier way to do this, such as to put all the domain controllers behind a name-space or address pool or something?
Nope. Being that you're static everywhere... you're stuck doing it the hard way. Take this as an opportunity to use DHCP + reservations for what you want static.
-
One thing to note, is that once you demote the old DC, you can easily change the IP of the new Server 2016 DC. It changes everything automatically these days.
Starting at Step 2 below, do following steps quickly.
-
Bring up new DC in parallel to the old one.
-
Transfer FSMO roles to new DC.
-
Demote old DC with DCPROMO.
-
Turn off old DC.
-
Set IP on new DC to what the old DC IP was. Possilble reboot new DC.
-
Verify DNS stuff reflects new DC having correct IP.
-
On a test client/user PC, do an
ipconfig /flushdns, maybe even a reboot. -
On a client/user PC, do an NSLOOKUP to domain.com.
-
On a client/user PC, enter
set log, verify it returns the correct DC.
-
-
@tim_g said in Using name-spaces or address pools for domain controllers? (things to make replacing DC's easier):
One thing to note, is that once you demote the old DC, you can easily change the IP of the new Server 2016 DC. It changes everything automatically these days.
Starting at Step 2 below, do following steps quickly.
-
Bring up new DC in parallel to the old one.
-
Transfer FSMO roles to new DC.
-
Demote old DC with DCPROMO.
-
Turn off old DC.
-
Set IP on new DC to what the old DC IP was. Possilble reboot new DC.
-
Verify DNS stuff reflects new DC having correct IP.
-
On a test client/user PC, do an
ipconfig /flushdns, maybe even a reboot. -
On a client/user PC, do an NSLOOKUP to domain.com.
-
On a client/user PC, enter
set log, verify it returns the correct DC.
See now this was my original plan like a year ago... almost everyone strongly advised against using the same IP for the new DC..
-
