Locally hosted external presence - best practices
I have some questions in general about the locally hosted external presence i have implemented and use.
we host our schools external services locally on a fairly nice 5mb symmetrical link which provides us with about 4 usable public IPs. At present our external services all run off the one IP i have set as the red side of our external firewall, and ofcourse our A, MX and CNAME records all point (or end up pointing to) that 1 ip address.
So - www.school.com; mail.school.com; fileaccess.school.com; all resolve to the one IP, being the red interface of the frotn end firewall, after processing this then passes on to the orange interface of the backend firewall (isa 2k4) which then again after processing passes to the green interface of the backend firewall and any relevent server traffic get forwared to the server segment.
Easier break down is here. (from a previous core network question i had, but this describes the server segment inrelation to the 2 firewalls, and implmentation of, but not using of, the DMZ)
Is there a better way to configure the externally facing servers? As in - should i be utilising multiple public IP's opposed to resolving everything to one? Am i doing something wrong here, or i should be looking to do something in a more effective way?
Thanks alot for the info and help guys!!