vaworx
asked on
unix to windows dns
We have the following scenario:
Windows 2003/2008 Servers and Exchange 2003 running on the following domain
region.mydomain.com
All DNS is currently performed by two BIND 9.2 Linux servers. There are two zones external and internal. Also our parent domain mydomain.com is controlled by a Linux box. Our primary network where about 1000 users login is REGION, all users under REGION receive email from Exchange under username@mydomain.com.
As planning on migrating to the region.local model apperas a greater challenge at the moment but we do need to implement dynamic DNS on REGION for all client workstation i wanted to get some opinitons on how you might have done it.
Our plan is to add DNS roles to both REGION Windows domain controllers which should do internal dynamic DNS so that a client machine registers A and PTR as pc1.region.mydomain.com internally, pc2.region.mydomain.com, etc. and for any non .REGION namespace the two windows DNS servers should forward to our Linux parent namespace.
We did consider BIND 9.2 configured as dynamic DNS but in terms of maintenance of all internal DNS, the Windows way appears easier with virtualy zero administration.
Any input would be greatly appreciated. Â Thanks.
Windows 2003/2008 Servers and Exchange 2003 running on the following domain
region.mydomain.com
All DNS is currently performed by two BIND 9.2 Linux servers. There are two zones external and internal. Also our parent domain mydomain.com is controlled by a Linux box. Our primary network where about 1000 users login is REGION, all users under REGION receive email from Exchange under username@mydomain.com.
As planning on migrating to the region.local model apperas a greater challenge at the moment but we do need to implement dynamic DNS on REGION for all client workstation i wanted to get some opinitons on how you might have done it.
Our plan is to add DNS roles to both REGION Windows domain controllers which should do internal dynamic DNS so that a client machine registers A and PTR as pc1.region.mydomain.com internally, pc2.region.mydomain.com, etc. and for any non .REGION namespace the two windows DNS servers should forward to our Linux parent namespace.
We did consider BIND 9.2 configured as dynamic DNS but in terms of maintenance of all internal DNS, the Windows way appears easier with virtualy zero administration.
Any input would be greatly appreciated. Â Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am not sure there is a right/wrong answer here, it's more a review is sought for a presented solution and two opinions are given on them.