Hi folks,
my question is really simple and the answer might be obvious to you but since I'm not and expert in Windows (and I'm asked to back my answer with examples) I would like to check it with you.
I have only found this thread similar in topic where the guy is putting a second DC with dynamic IP and nobody warns him from doing it, actually give him help.
http://social.technet.microsoft.com/Forums/en-US/5f0398de-d0cd-4a57-bc8b-a483a91ebd80/how-to-add-additional-domain-controller-to-a-primary-domain-controller-having-a-dynamic-ip-address?forum=winservermanager
As to my case, we have two DCs (on the same LAN) and recently a third one was added for redundancy reasons, reachable through VPN (setup by other devices).
I always apply the general rule SERVER => static IP address and this situation falls within it imo.
I should give management the answer on whether this is recommended/discouraged bringing examples of any hindrances/problems that in your opinion this could cause.
Thanks in advance, Alex
my question is really simple and the answer might be obvious to you but since I'm not and expert in Windows (and I'm asked to back my answer with examples) I would like to check it with you.
I have only found this thread similar in topic where the guy is putting a second DC with dynamic IP and nobody warns him from doing it, actually give him help.
http://social.technet.microsoft.com/Forums/en-US/5f0398de-d0cd-4a57-bc8b-a483a91ebd80/how-to-add-additional-domain-controller-to-a-primary-domain-controller-having-a-dynamic-ip-address?forum=winservermanager
As to my case, we have two DCs (on the same LAN) and recently a third one was added for redundancy reasons, reachable through VPN (setup by other devices).
I always apply the general rule SERVER => static IP address and this situation falls within it imo.
I should give management the answer on whether this is recommended/discouraged bringing examples of any hindrances/problems that in your opinion this could cause.
Thanks in advance, Alex