Sanity Check on Enterprise Architecture

5 msg	views/slaves/notify problem cures?
2 msg	Bind 9.3.3 on Solaris 9
5 msg	Internet Unknown (28)
2 msg	RBL entries in bind
4 msg	Does a zone file specify its domain name?
3 msg	Questions about my special DNS setting
21 msg	Changing output of bind
6 msg	Bind's logs
8 msg	Alternative to RFC2317 -- Classless Delegation
5 msg	Statistics file not working

Sanity Check on Enterprise Architecture
\ Eric Berg (8 Dec 2006)
. \ Stephen John Smoogen (8 Dec 2006)
. \ Kevin Darcy (9 Dec 2006)

4 msg	Newbie Questions
6 msg	Memory Leak in Bind 9?
1 msg	slpda via dhcp
1 msg	Newbie Questions about named (send it again)
1 msg	Newbie Questions about named
20 msg	error: bad dotted quad
1 msg	bind-9.4.0-b3: internal_send: 0.0.0.1#53: Inval...
1 msg	bind 9.3.2-P2 on Digital Unix 4.0D
1 msg	dig or nslookup to send TKEY query??

Subject:	Sanity Check on Enterprise Architecture
Group:	Bind-users
From:	Eric Berg
Date:	8 Dec 2006

I'm seeking some advice on how to architect a consolidated DNS
infrastructure for my company.

We are moving toward consolidating our DNS infrastructure by
implementing Sauron (OSS DNS mgmt system, CLI + Web) for management, and
by putting a single set of master bind servers in place from which all
other network-specific servers would perform zone transfers to get their
data.

The other option that we're looking at, and that would also serve as an
interim step to the solution in the previous paragraph, is to create
zone configurations for each of our network-specific bind servers on an
individual basis and push them to the servers from a central point.

Among the reasons that we're looking to implement a set of master
servers which would contain all of the DNS information for all hosts in
all of our networks are the following:

* We are trying to consolidate the management of DNS as much as
possible.
* We occasionally connect previously isolated networks and then need
to make hosts in each network resolvable to one another
* It cuts down on the amount of back-and-forth (things that can
break) by doing zone transfers instead of creating jobs to push
zone files on a daily basis. It seems to me that once the data is
in bind, the zone transfer would be the cleanest way to populate
the other bind servers.

It's a high-level question, but I'm hoping that anyone with experience
managing multiple DNS servers (on the order of 30 or more) with about as
many subdomains can provide some insight into how to think about this
problem as well as any gotchya's we might run into.

Thanks very much.

-Eric.