Parent / CHild Domain Setups

I am one of the "Experts" here but I don't have a good answer to this and I need to seek some more suggestions.  At my work I have the Corporate location in one city and 5 other plants at 5 other cities.  We currently use Linux and are in the process of moving over to Active Directory using Windows Server 2008 R2.  I wanted to use a Parent / Child domain structure and use as the child domain and as the Corporate location.  Each location has a different IP scheme 10.XX.0.0 and the XX changes per plant.  One of the main problems that I have is that we are using Custom written software and it is using the same server names at each location on a flat network.  So each fileserver points to 10.(local XX).1.1 but I am having an issue of getting to let me point it differently at each plant while trying to set up AD.  I have issues with that since the Active Directory replicates between the main location to the sites.  Thanks everyone.
Trent SmithAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi Trent,

If you're looking for a single setting to change, you probably won't find one. Microsoft moved away from the "parent/child" topology years ago, replacing it with the forest structure. That said, you'll probably have a better understanding after reading this:

DNS subnet prioritization might do it for you.

You can use hosts file entries to force machines to a specific IP for a server name. Either way I would avoid having an actual server called filserver.

Final option I can think of is to setup a DFS namespace on fileserver and that namespace can point to the local fileservers as long as you don't have unique files in the root of the share.

Windows 2008 R2 is in extended support now and has less than 5 years left. Go for 2012 R2 if you can.

I can elaborate on any suggestion as you may require.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Trent SmithAuthor Commented:
We have the plan to move to 2012 but we are putting 2008 in first.  This domain has always been on Linux so one baby step at a time.
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Trent, what do you think of my suggestions?

FWIW, personally I think it would be easier to just deploy 2012 R2 first instead of upgrading to it later. I would also virtualize all of new Windows servers.
Trent SmithAuthor Commented:
This is just what I needed.  Thanks for the help.  It worked great.
Which proposal? I gave three.
Trent SmithAuthor Commented:
DNS Subnet prioritization.
Cool. Just wanted to know so others that find this question will know which solution worked for you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.