Re: FW: Delegating reverse DNS to a customer

2009-08-22 Thread Chris Hills
On 18/08/09 20:32, Kevin Darcy wrote: No, you can't do a "sideways" delegation like that. The correct solution, as stated elsewhere, is to get 251.250.63.in-addr.arpa delegated directly from ARIN to the customer. Strictly speaking it is legal to use DNAME at the apex of a zone since DNAME onl

RE: FW: Delegating reverse DNS to a customer

2009-08-19 Thread Tim Huffman
ginal Message- > From: bind-users-boun...@lists.isc.org [mailto:bind-users- > boun...@lists.isc.org] On Behalf Of Kevin Darcy > Sent: Tuesday, August 18, 2009 1:33 PM > To: bind-users@lists.isc.org > Subject: Re: FW: Delegating reverse DNS to a customer > > bsfin...@anl.gov wrote: &

Re: FW: Delegating reverse DNS to a customer

2009-08-18 Thread Kevin Darcy
bsfin...@anl.gov wrote: On Tue, Aug 18, 2009 at 8:31 AM, Tim Huffman wrote: 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 t

FW: Delegating reverse DNS to a customer

2009-08-18 Thread bsfinkel
On Tue, Aug 18, 2009 at 8:31 AM, Tim Huffman wrote: > 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

Re: Delegating reverse DNS to a customer

2009-08-18 Thread Mark Andrews
In message , Chris Hills writes: > On 18/08/09 15:55, Ben Bridges wrote: > > 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

Re: Delegating reverse DNS to a customer

2009-08-18 Thread Chris Hills
On 18/08/09 15:55, Ben Bridges wrote: 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 authorit

RE: Delegating reverse DNS to a customer

2009-08-18 Thread Ben Bridges
[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) I

FW: Delegating reverse DNS to a customer

2009-08-18 Thread Tim Huffman
Thanks for your help! > > -Original Message- > > From: aad [mailto:ali.da...@gmail.com] > > Sent: Tuesday, August 18, 2009 8:13 AM > > To: Tim Huffman > > Subject: Re: Delegating reverse DNS to a customer > > > > Hi Tim, > > > > Gi

Re: Delegating reverse DNS to a customer

2009-08-18 Thread Ben Croswell
The issue is probably that you need to delegate the 251.250.63.in-addr.arpa to your client in the 250.63.in-addr.arpa zone. If you load 251.250.63.in-addr.arpa to try and delegate it, your servers will answer for it because they load it. Think of it in the same mind of delegating a forward subdoma

Delegating reverse DNS to a customer

2009-08-18 Thread Tim Huffman
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