Apologies in advance for the off-topic question...
I've heard many comments in this community lately about NOT manually assigning a static ip address to servers. This is extremely intriguing. Is it simply a bulletproof DHCP and DNS configuration? Are ip addresses still "assigned" via DHCP reservation?
Can anyone point me in the proper direction to learn the best way to accomplish this? Is there a design guide or Microsoft "best practice"?
Roughly speaking, you would configure and deploy the server with a Configuration management system such as PowerShell DSC, Puppet, Chef etc. Part of this process would be placing the server behind a load-balancer for example, removing the need for to know specific IP address, or even needing to know the name of the server. The idea being, the less personal you need to get with each individual server, the quicker you can deploy and destroy your servers as need arises.
All the best
Most IT production shops do not allow DHCP, most test & dev would not survive without it. We do not want someone booting up a server in production area and getting an IP without approval, hence manual processes. Still there are ways to do DHCP in production area where only known MAC addresses are given predetermined IP addresses.
In test & dev, the problem is if your server goes offline for a little while and lease expires, you might loose that IP. But using a DNS for naming (i.e., for connecting to servers by name instead of IP) will overcome that.
You must be logged in to reply to this topic.