DNS/Active Directory

[efector]

Hello. I am inherited a messy AD Domain/DNS. Our ROOT domain is US.ifm . Now, we are responsible for all IT operations in north america(including CANADA/Mexico). Some brain surgeon before me decided to create a TRUST between Mexico and the US, but made it a CHILD domain of the US.IFM . I have NO CLUE why they didnt make it the FQDN of the company, but thats another story. My question is this, since our office has many sites in the US, wouldnt it be prudent to use subdomains under the US.IFM? Example: if we had a Houston TX office, it would be hou.tx.us.ifm? As it stands now, ALL offices, except mexico, come directly under the US.IFM zone files. The next question, would be HOW to get the computers to be a part of that zone file? Example: when you look at a computers name, its say 'server.us.ifm', how can I get it to change to 'server.hou.tx.us.ifm'? Also, for the client machines, if I put in the parent domain under the DHCP settings as 'hou.tx.us.ifm' will that change their information and register them appropriately under DNS?

Its a mess, and I dont know where to start.

Thanks in advance

 

[markdmac]

Why go with child domains at all? Why not seperate your sites using OUs. The management is easier that way.

About the only reason to give them their own site would be to cut down on replication traffic. If you are making them their own domain then they obviously have their own DC. So, local logon times would be good as authentication over the WAN is not needed. So what do you hope to gain by using child domains?

I hope you find this post helpful.

Regards,

Mark