Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!caen!ox.com!ox.com!emv From: emv@ox.com (Ed Vielmetti) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: Multiple Primary Name Servers Message-ID: Date: 12 Dec 90 05:48:26 GMT References: <2726@hsi86.hsi.com> Sender: usenet@ox.com (Usenet News Administrator) Organization: OTA Limited Partnership, Ann Arbor MI. Lines: 19 In-Reply-To: wright@hsi86.hsi.com's message of 11 Dec 90 15:30:31 GMT 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