Breaking up a class for delegation
dawn.connelly at gmail.com
Mon Sep 24 20:03:58 UTC 2007
Either you do a redelegation on the current authoritative name servers or
you redo your IP address space with ARIN who would then change the
delegation at the root servers. Either way would work. The first way might
be less administrative paperwork.
On 9/24/07, Bischof, Ralph F. (MSFC-NNM04AA02C)[SAIC] <
Ralph.Bischof at nasa.gov> wrote:
> Hello all,
> This may not be a BIND-specific question. If so, I apologize. I
> also have looked at RFC2317. Here is my dilemma:
> I have 18.104.22.168/16 that is delegated to a Center (see
> http://ws.arin.net/whois/?queryinput=N%20.%20NASA-IVV). Since the Center
> is not using the whole B, they decided to give away the upper half to a
> project within NASA that is needing space. Yet, the original Center does
> not want to be responsible for the upper half. Therefore, I must look at
> delegating half of the B to one entity and the other half to the other.
> My thought is that instead of having a single delegation to the
> two nameservers as I do now, I will have to take the single delegation
> (164.129.in-addr.arpa) and give it 256 entries. The first 128 entries
> would be delegations to at least two nameservers for the original Center
> and the second set of 128 entries to at least two nameservers for the
> new project. Then, each of the two delegatees (is that a word?) would
> need to also build up 128 zone files as they saw fit.
> Is there another way? If not, I am good with that idea. I just
> wanted to make sure that I have not missed something that has come out
> Thank you,
> Ralph Bischof
> The opinions expressed in this communication are not necessarily those
> of NASA.
More information about the bind-users