E
eric romero
Hi all,
I have an AD forest 1 forest, 1tree , childdomains. Running on windows2003
(some child still on windows2000) using microsoft DNS. I anticipate mor
childomains are going to join this forest.
Please do yuo have any comments on replacing the current DNS & DHCP servers
(root and childomains) by a third-party software such Incognito ip/dns
commander.
Having in count that my forest is alerady running root+several childomains ,
how can I deploy the new non-microsoft dns.
Do you have any comments in general of replcaing the microsoft DNS by a
"compatible" dns. I am worry about future implications such as Adding new
childomains, removing/adding global catalogs on the root or childomains,
deploying exchange2003, monitoring replication all these tasks rely on
microsoft DNS, itis hard for me to prevent future behavior of all these
tasks (and some others I am not aware of) when a non-microsoft dns is in
place.
So far the advantage of going to the non-microasoft dns is that one of the
features of this third-party product is that it will block the assignmentof
dhcp ips to non-company pcs (i.e if a vendor comes in these new dhcp will
not assign an ip unless an admin authorize it.)
thx
I have an AD forest 1 forest, 1tree , childdomains. Running on windows2003
(some child still on windows2000) using microsoft DNS. I anticipate mor
childomains are going to join this forest.
Please do yuo have any comments on replacing the current DNS & DHCP servers
(root and childomains) by a third-party software such Incognito ip/dns
commander.
Having in count that my forest is alerady running root+several childomains ,
how can I deploy the new non-microsoft dns.
Do you have any comments in general of replcaing the microsoft DNS by a
"compatible" dns. I am worry about future implications such as Adding new
childomains, removing/adding global catalogs on the root or childomains,
deploying exchange2003, monitoring replication all these tasks rely on
microsoft DNS, itis hard for me to prevent future behavior of all these
tasks (and some others I am not aware of) when a non-microsoft dns is in
place.
So far the advantage of going to the non-microasoft dns is that one of the
features of this third-party product is that it will block the assignmentof
dhcp ips to non-company pcs (i.e if a vendor comes in these new dhcp will
not assign an ip unless an admin authorize it.)
thx