wright@hsi86.hsi.com (Gary Wright) (12/11/90)
Some background: We have a class B network that is subnetted and spans two geographically and administratively distinct sites. We would like to find a manageable way to update the in-addr.arpa domain for this network without either site totally relying on the other. One possibility that has been suggested is to have a primary name server for the domain at both sites and to also mark each as a secondary for the other. In this way, hosts could be added or deleted from one site even while the primary name server at the other site is un-available (network problems, administrator on vacation etc.) Does the DNS allow for multiple primary name servers for a zone? If so what interaction occurs between the primaries? Is there a better way to handle this problem? Any tips would be appreciated. -- Gary Wright ...!uunet!hsi!wright 3M Health Information Systems wright@hsi.com
emv@ox.com (Ed Vielmetti) (12/12/90)
In article <2726@hsi86.hsi.com> wright@hsi86.hsi.com (Gary Wright) writes:
We have a class B network that is subnetted and spans two
geographically and administratively distinct sites.
We would like to find a manageable way to update the in-addr.arpa
domain for this network without either site totally relying on
the other.
Allocate authority in-addr.arpa authority separately for each of the
subnets involved. If the net is neatly divided into two parts, that
might just mean cluttering up the first level of the in-addr.arpa
domain with a mess of NS records, one for each subnet.
The "211.141.in-addr.arpa" domain is divided more or less this way,
you might use your favorite domain lookup program (dig is mine) to see
how that's split up.
--Ed
emv@ox.com