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

method


Click on the red underlined text to get to the source

... address spaces covering fewer than 256 addresses. The proposed method should thus remove one of the objections to subnet ...
... authority for the corresponding IN-ADDR.ARPA mappings. The proposed method is fully compatible with the original DNS lookup mechanisms specified in [1 ...
... The document also discusses some operational considerations to provide some guidance in implementing this method. ...


... IN-ADDR.ARPA") zone autonomously. By use of the reverse delegation method described below, the most important objection to assignment of longer prefixes to unrelated ...
... 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. ...


... 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. ...
... For each size-256 chunk split up using this method, there is a need to install close to 256 CNAME records in the parent zone. Some ...


... delegations covering larger blocks of addresses the traditional methods (multiple delegations) can be used instead. ...
... As a result of this method, the location of the zone containing the actual PTR records is no longer predefined. This gives flexibility and some examples will be presented here. ...
... IN-ADDR.ARPA tree). It would be necessary to use one of these alternate methods if two organizations somehow shared the same physical subnet ...



Google
Web
RFC-Ref