Re: DNS combining multiple domains

• Subject: Re: DNS combining multiple domains
• From: Bret Alan <email@hidden>
• Date: Sun, 20 Nov 2005 23:20:16 -0500
• Delivered-to: email@hidden
• Delivered-to: email@hidden

At 11:01 PM -0500 11/19/05, Bret Alan wrote:

At 2:06 PM -0500 11/19/05, Bret Alan wrote:

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?

Because these schools were not connected together in any way until this month.

But you've already stated that they are now connected via a WAN, which was why I asked.

Forwarding to your network provider for what exactly? Zones not local?

Forwarding to their DNS servers for resolving all public domain names. I know this is not necessarily the best way to do this, but originally we did not want to have to worry about updating a bunch of separate server's root hints files, so we set them all up as forwarding servers, which is described as being acceptable in DNS & Bind.

I can't remember the last time I had to update the list of root servers.

Ok. Good to know.

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.

Wouldn't this mean that we would have to setup a separate zone for each school domain on every server?

Sounds like you already had that. school1.lan, school2.lan, ...

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".

Ok. I think that clarifies my last question. So setup each server to do zone tranfers for it's own domain to every other server?

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

Again, just because we started with separate domains, so we currently have ns.school1.lan and ns.school2.lan, etc. So if we change to one domain, we would have to change each server's host name (not that difficult, since there aren't that many static dns records anyway).

I don't see how this matters. Nor did I suggest switching to one zone, though you could.

So, I take it you would recommend changing to one domain, and changing some of the other servers to domain slaves for redundancy, instead of doing zone tranfers with the multiple domains?

First, we're talking about "zones", not domains, when we talk about DNS hosting, and understanding the distinction is important. I think it's one reason why you're having trouble wrapping your head around this. When you start thinking in terms of zones, you can begin to think of how multiple "domains" can be placed into zones to make this all trivial.

But I didn't suggests what you describe here at all, but sure, you could. Nor am I sure why you'd consider multiple slaves. They could just forward to you servers as easily, in fact more easily, and the recurse on from their if needed. Since you'd be caching, this would be very efficient.

My suggestion was to have one zone, for all your schools, keeping their current bogus domains, have all your schools use a set of central DNS servers, that could run views, and call it a day.

Thanks for your help.

Bret

--

-dhan

------------------------------------------------------------------------
Dan Shoop                                                   AIM: iWiring
Systems & Networks Architect                     http://www.iwiring.net/
email@hidden                                 http://www.ustsvs.com/

pgp key fingerprint: FAC0 9434 B5A5 24A8 D0AF  12B1 7840 3BE7 3736 DE0B

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

• Follow-Ups:
  • Re: DNS combining multiple domains
    • From: Dan Shoop <email@hidden>

• Prev by Date: Re: Change IP & Gateway
• Next by Date: Re: DNS combining multiple domains
• Previous by thread: Re: DNS combining multiple domains
• Next by thread: Re: DNS combining multiple domains
• Index(es):
  • Date
  • Thread