Since the CIDR block you have been allocated containing 63.250.251.0/24 is smaller than a /16, ARIN is delegating authority for the IN-ADDR.ARPA zones for each of your /24's directly to your dns servers. In order for your customer's dns servers to be authoritative for 251.250.63.IN-ADDR.ARPA, you're going to have to have ARIN delegate the zone to your customer's servers. If you have not already SWIP'ed the /24 to your customer, then you'll want to do so using the detailed reassignment template (https://www.arin.net/resources/templates/reassign-detailed.txt, I think). If you have already SWIP'ed the space to them, then you'll need to submit the net-mod template (https://www.arin.net/resources/templates/netmod.txt, I think) for the /24. (Note: I'm not the person who submits SWIP templates in our organization, so I might be wrong about the particular templates to use. But the principle is still valid. It's the SWIP information filed with ARIN that determines what dns servers are authoritative for the in-addr.arpa zones for your /24's.) Ben
________________________________ From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Tim Huffman Sent: Tuesday, August 18, 2009 7:32 AM To: bind-users@lists.isc.org Subject: Delegating reverse DNS to a customer Guys, We're a smallish (but growing) ISP, and we've been asked by one of our customers to delegate reverse DNS for 63.250.251.0/24 to their DNS servers, ns1.emns.com - ns4.emns.com. Unfortunately, we've never had to delegate DNS to a customer before, and we're having problems getting it to work. We're running BIND 9.5.1 on Fedora. Can anyone give me an example of how this should be done in named.conf and the file 251.250.63.in-addr.arpa.zone? I'd appreciate it! -- Tim
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users