I know I might get roasted for this. The standard best practice is to "let routers route and servers serve" when it comes to having your firewall set as static and Windows server handle dhcp and dns, but I'm looking for some in depth logic for why it wouldn't make sense to let a firewall run these networking roles. I can see a few added benefits , the most prominent being that web services would not be interrupted by a domain controller reboot. Firewalls have to be reboot far less often then a domain controller , especially in current iterations of server. Would it make domain authentication any slower? Would it make management of computers any less doable ? What would be the pros and cons?
please don't just Porrot "Because that's the way it's done".
No comments:
Post a Comment