Server DHCP Adresses

Burnsy2023 · 7 Apr 2009 at 11:46

Ok, so I have a collegue who thinks it's ok to assign DHCP addresses to a server interface.

So to highlight how very stupid this is lets compile a list of potential issues that could occur from this. I'll start:

Potential DNS inconsistencies which cause AD replication issues.

You really can't get the staff these days

Burnsy2023 · 7 Apr 2009 at 12:39

iaind said:
Depends what the server is TBH...

Domain controller, file, print and various other bits and bobs.

Burnsy2023 · 7 Apr 2009 at 12:46

iaind said:
I thought Windows prevented you from DCPromo'ing a box if it had a static IP? Or is that just DHCP servers...

For those cases it's a bit stupid but I have to admit I've got some boxes that I've left on DHCP out of lazyness, but only "utility" type boxes that arent accessed by users so dont necessitate a static IP

Dcpromo does check that, but it was changed afterwards :mad:

Burnsy2023 · 7 Apr 2009 at 12:59

Sin_Chase said:
If there is a MAC reservation there should not be any problems, without however.....lol.

What other problems do you envisge?

Burnsy2023 · 7 Apr 2009 at 15:57

But conveluted though. What would be the benefits?