Would this be the right thinking for child domains?

Hi,


I am building out a sharepoint environment, which would have dev/prod domains (mentioned before in a previous thread). However, I will also be hosting a number of infrastructure servers in the network such as WSUS, DHCP, WDS, etc. Obviously the Sharepoint environments need visibility of this as DHCP needs to serve many servers in the entire network, regardless of where they are in the domain structure.

I am thinking that I can create two child domains under a parent domain called say INFRASTRUCTURE (which hosts relevant infrastructure servers), which comprise of the respective dev and prod sharepoint environments.


Is there any flaw in this design? It's either this or 3 seperate flat domains under the forest.



Thanks