RFC 2317:Classless IN-ADDR.ARPA delegation
RFC-Ref

address


Click on the red underlined text to get to the source

... IN-ADDR.ARPA delegation on non- octet boundaries for address spaces covering fewer than 256 addresses. The proposed method ...
... octet boundaries for address spaces covering fewer than 256 addresses. The proposed method should thus remove one of the ...
... objections to subnet on non-octet boundaries but perhaps more significantly, make it possible to assign IP address space in smaller chunks than 24-bit prefixes ...


... With the proliferation of classless routing technology, it has become feasible to assign address space on non-octet boundaries. In case of a very small organization with only a few hosts, assigning a full ...
... class C network number") often leads to inefficient address space utilization. ...
... One of the problems encountered when assigning a longer prefix (less address space) is that it seems impossible for such an organization to maintain its own reverse ("IN-ADDR.ARPA") zone autonomously. By ...
... Let us assume we have assigned the address spaces to three different parties as follows: ...
... zone can only be delegated once, and this usually translates into "this zone can only be administered by one organization." The other organizations with address space that corresponds to entries in this zone would thus have to depend on another organization for their address ...
... address space that corresponds to entries in this zone would thus have to depend on another organization for their address to name translation. With the proposed method, this potential problem can be avoided. ...


... IN-ADDR.ARPA tree downwards, e.g. by using the first address or the first address and the network ...
... tree downwards, e.g. by using the first address or the first address and the network mask length (as shown below) in the corresponding address space ...
... address and the network mask length (as shown below) in the corresponding address space to form the the first component in the name for the zones. The following four zone files show how the problem in the motivation section could be solved using this method ...
... resource records in the parent zone once and for all, if the way the address space is partitioned is known. ...
... in the DNS does not have to be modified to accommodate this splitting of the responsibility for the IPv4 address to name translation on "non-dot" boundaries. Furthermore, this technique has been in use for several years in many installations, apparently with no ill ...


... This technique is intended to be used for delegating address spaces covering fewer than 256 addresses. For delegations ...
... This technique is intended to be used for delegating address spaces covering fewer than 256 addresses. For delegations covering larger blocks of addresses ...
... addresses. For delegations covering larger blocks of addresses the traditional methods (multiple delegations) ...
... An alternative to using the first address, or the first address and the network ...
... An alternative to using the first address, or the first address and the network mask length in the corresponding address space ...
... address and the network mask length in the corresponding address space, to name the new zones is to use some other (non-numeric) name. Thus it is also possible to point to an entirely different part of the DNS tree ...
... shared the same physical subnet (and corresponding IP address space) with no "neat" alignment of the addresses, but still wanted to ...
... subnet (and corresponding IP address space) with no "neat" alignment of the addresses, but still wanted to administrate their own IN-ADDR.ARPA mappings. ...
... This way you can actually end up with the name->address and the (pointed-to) address->name mapping data in the same zone file - some ...
... This way you can actually end up with the name->address and the (pointed-to) address->name mapping data in the same zone file - some may view this as an added bonus as no separate set of secondaries for the reverse zone is required. Do however note that the traversal via ...
... Note that one cannot provide CNAME referrals twice for the same address space, i.e. you cannot allocate a /25 prefix to one organisation, and run IN-ADDR.ARPA ...


... in the IN-ADDR.ARPA domain, thus making it possible to assign address space more efficiently without losing the ability to delegate the DNS authority ...
... DNS authority over the corresponding address to name mappings. ...


... Authors' Addresses ...



Google
Web
RFC-Ref