It sounds like you have a single domain environment, is that correct? Is the user distribution fairly even among the sites?
Merely creating a DC at each site will not solve bandwidth problems. Log-ons require the services of a Global Catalog server. Once you create the DC at each site, enable it as a Global Catalog server; otherwise the log-on process would still propagate to your main DC for user authentication.
DCs at each site will create other bandwidth issues because of the AD replication process. However, you can control this through scheduling.
You might consider changing your DNS to use Active Directory-Integrated Zones. This way DNS info is replicated at the same time AD is replicated. That way, every DNS server will maintain the same zone information without a separate DNS replication process (because the zone information is maintained within AD).
Implemented in this way, the computer configuration you cite should suffice. You could schedule AD replicationto occur only during non-business hours. User authentication would take place on the local copy of AD (assuming the Global Catalog server is also local). The only remaining issue would be server load determined by the number of servers being hosted and the average size of print jobs at each site.
Good Luck.