Your main AD server should have DNS on it. DHCP is not a requirement, AFAIK.
AD and DNS work closely together and having DNS no a different server adds additional chances for failure.
Performance would be minimized by having them together. DHCP, on the other hand, is not a big issue, depending on how long you set your leases.
Querying for a DHCP server obtaining an address is not a big deal compared to naming an authentication.
Let's also be clear on something else. An AD server with DNS/DHCP, etc. should not a file server. The Microsoft domain models for client/server networking do not lend themselves to the all eggs in one basket approach.