Where is V18 at?

cryptochrome said:

 

The point I am trying to make is that not everything is a small business and you can't apply general assumptions to everyhing. I think some of you would be really surprised if you worked for a large enterprise once. No one in their right mind would ever put DNS and DHCP on their firewalls in those kind of networks. 

 

 

That's quite often because you can't - most large enterprises use active directory, which requires a hefty integration with DHCP and DNS.

If you read the comments of why people are wanting DNS and DHCP, these aren't for large enterprises, but for SME's - and to be honest there is no reason why a perimeter device for a SME cannot be a firewall, DNS and DHCP server.

The point here is that the device is capable should it be required, but can be disabled if not - so suits large and SMEs

BLS said:

 

That's quite often because you can't - most large enterprises use active directory, which requires a hefty integration with DHCP and DNS.

That is most often not the reason. Look, I don't want to sound like a smart ass, but as a freelancer I've been working for quite a lot of large scale enterprises and carriers for the better part of the past 20 years. More than I can count. And it is just common sense there to not "misuse" firewalls for anything other than firewalling (in broader terms). Because they can't is one of the reasons, but certainly not the most common one. The most common reason is actually that they have the resources to be able to design their networks and services properly. Single points of failure are usually avoided at all cost.

Even if they are heavy Microsoft shops they tend to use dedicated IP services tools (IPAM) for DNS and DHCP, stuff like Infoblox, Cisco Prime, Bluecat, QIP or even BIND (yikes). 

 

The point here is that the device is capable should it be required, but can be disabled if not - so suits large and SMEs