we have been running each school in our district (each one with its
own Mac OS X Server running Bind) as their own private DNS domain
(all forwarding to our network provider for public DNS):
You're running each school as a separate zone? Why not run one big
zone for all schools?
Forwarding to your network provider for what exactly? Zones not local?
school.lan 10.10.1.0/24
school2.lan 10.10.2.0/24
etc.
Now the schools are connected in a WAN, but each still with the same
private subnet 10.10.X.0/24.
What's the best way to approach sharing the DNS info across these
domains, so that a lookup for ns.school2.lan is resolved on any
other schoolX.lan subnet?
Use zone transfers. Maybe use Views like you should be.
One master DNS server with a forward and reverse zone for each
domain, with a slave at each school?
Maybe, if you're a control freak and like to have central control.
You could just have them each do zone transfers tpo each other and
leave control for each zone local to each of these "schools".
Of course why bother to have a DNS server in each school, sounds like
you just need one on your network that holds all the zones and
everything using it as their DNS server...
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.iwiring.net/
email@hidden http://www.ustsvs.com/
iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
