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
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
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'
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
4 matches
Mail list logo
