B
barry
quick scenario overview:
My company have about 150 remote stores around the company, connecting to
Head Office via VPN. They are in a child domain of the domain in HO.
Obviously looking to their own DNS servers to find DCs etc. Now, we'd like a
way to manage what sites they can visit on the interweb. Currently the best
(ie cheapest...) is to not allow them to find the IP for domains, however,
the DNS of the child domain forwards anythnig upwards to the parent.
So my theory is as follows:
If we set the child domain dns servers to be authorative for "." Then they'll
never forward any requests outwards and we can simplay add in zones for
sites that we want them to visit. But, then they wont know how to talk to
the parent domain unless I make it authorative for that domain too, which is
ok. But as it's a child domain, is it going to cause any problems with it
being authorative for its parent?
Is the above even possible?? Am I talking rubbish?? Any better ideas??
Cheers for any info
barry
My company have about 150 remote stores around the company, connecting to
Head Office via VPN. They are in a child domain of the domain in HO.
Obviously looking to their own DNS servers to find DCs etc. Now, we'd like a
way to manage what sites they can visit on the interweb. Currently the best
(ie cheapest...) is to not allow them to find the IP for domains, however,
the DNS of the child domain forwards anythnig upwards to the parent.
So my theory is as follows:
If we set the child domain dns servers to be authorative for "." Then they'll
never forward any requests outwards and we can simplay add in zones for
sites that we want them to visit. But, then they wont know how to talk to
the parent domain unless I make it authorative for that domain too, which is
ok. But as it's a child domain, is it going to cause any problems with it
being authorative for its parent?
Is the above even possible?? Am I talking rubbish?? Any better ideas??
Cheers for any info
barry