On 22.07.13 12:29, Ryan Pavely wrote:
I always thought I had to break up the CIDR's into the proper blocks so then my downstream customer can slave that partial zone. I don't want them slaving 10.10.1/24... etc.. So to do that you break up the block into all its parts, each with an origin, ttl, etc etc... So now it appears I need both the 10.10.1.rev and each 10.10.1.XX-YY.rev file. Seems redundant.
It's not redundant. The /24 block owner has its own 1.10.10.in-addr.arpa zone which contains CNAMEs pointing to other zones. The clients have those "other zones" which the owner should slave. It's just recommended to give those zones names like 0/27.1.10.10.in-addr.arpa so it's clear what the zone does. Example is 1.1.10.10.in-addr.arpa CNAME 1.0/27.1.10.10.in-addr.arpa in the reverze zone. This will cause the lookups go to 0/27.1.10.10.in-addr.arpa maintained by the client. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. BSE = Mad Cow Desease ... BSA = Mad Software Producents Desease _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
