I have a fairly large project tasked to me, and this is my first experience with DNS administration, so the entire process is a learning experience.
Currently, we have the following infrastructure.
A single active directory integrated domain zone for our exchange environment.. call it companyglobal.com, which is hosted on domain controllers for companyglobal.com
We have 3 other AD domains(seperate from that) that we're consolidating usa.com, eur.com and asia.com. These domains are in the process of being merged with companyglobal.com The DNS zones for these are hosted in BIND. We have 4 zones in bind. boston.amer.company.com canada.amer.company.com (both of those belong to the usa.com domain) dublin.emea.company.com (part of eur.com) and china.company.com (part of asia.com)
The question(s) I have are... our goal is to consolidate down to a single domain (companyglobal.com) however we want to be able to allow static clients(we're in software dev and have hundreds of unix hosts) which need to keep the older domains (boston.amer.company.com) while the DHCP clients will register themselves with their domain companyglobal.com
Second is it possible to get a host to automatically register itself in companyglobal.com AND boston.amer.company.com?
Third, with windows clients being a member of companyglobal.com, I assume will automatically register themselves as client.companyglobal.com If there was a reason for them to HAVE its primary DNS suffix be client.boston.amer.company.com is my only option to use a static/reserved address and create an A record manually?
Apologies for the length of the post. This will probably spawn more questions as well. I just finished my 70-291 exam, and while the book content is still fresh in my head, it's a bit different trying to plan an actual migration to an existing environment, that isn't picture perfect microsoft.
Currently, we have the following infrastructure.
A single active directory integrated domain zone for our exchange environment.. call it companyglobal.com, which is hosted on domain controllers for companyglobal.com
We have 3 other AD domains(seperate from that) that we're consolidating usa.com, eur.com and asia.com. These domains are in the process of being merged with companyglobal.com The DNS zones for these are hosted in BIND. We have 4 zones in bind. boston.amer.company.com canada.amer.company.com (both of those belong to the usa.com domain) dublin.emea.company.com (part of eur.com) and china.company.com (part of asia.com)
The question(s) I have are... our goal is to consolidate down to a single domain (companyglobal.com) however we want to be able to allow static clients(we're in software dev and have hundreds of unix hosts) which need to keep the older domains (boston.amer.company.com) while the DHCP clients will register themselves with their domain companyglobal.com
Second is it possible to get a host to automatically register itself in companyglobal.com AND boston.amer.company.com?
Third, with windows clients being a member of companyglobal.com, I assume will automatically register themselves as client.companyglobal.com If there was a reason for them to HAVE its primary DNS suffix be client.boston.amer.company.com is my only option to use a static/reserved address and create an A record manually?
Apologies for the length of the post. This will probably spawn more questions as well. I just finished my 70-291 exam, and while the book content is still fresh in my head, it's a bit different trying to plan an actual migration to an existing environment, that isn't picture perfect microsoft.