[Pdns-users] in.addr-arpa delegation

[Kai]

On Wed, Feb 22, 2006 at 04:32:36PM -0800, Max Clark wrote:
> Hi all,
> 
> I have a couple of questions on delegation with PowerDNS. To delegate
> subnets smaller than a /24 (let's say 10.0.0.0/29) I have been
> creating records like this:
> 
> 0/29.0.0.10.in-addr.arpa ns ns1.foo.com
> 0/29.0.0.10.in-addr.arpa ns ns2.foo.com
> 
> and then:
> 
> 1.0.0.10.in-addr.arpa CNAME 1.0/29.0.0.10.in-addr.arpa
> 2.0.0.10.in-addr.arpa CNAME 2.0/29.0.0.10.in-addr.arpa
> 3.0.0.10.in-addr.arpa CNAME 3.0/29.0.0.10.in-addr.arpa
> 4.0.0.10.in-addr.arpa CNAME 4.0/29.0.0.10.in-addr.arpa
> 
> in my 0.0.10.in-addr.arpa zone file.
> 
> First question - is there an easier/better way to do this?

Hi Max,

There is something I've only discovered a few months ago which seems to
nicely work.

Instead of delegating the weird and nonstandard '0/29', you actually can
delegate 0 through 15 by only supplying NS records:

$ORIGIN 0.0.10.in-addr.arpa.
0	IN	NS	ns1.foo.com.
	IN	NS	ns2.foo.com.
1	IN	NS	ns1.foo.com.
	IN	NS	ns2.foo.com.
2	IN	NS	ns1.foo.com.
	IN	NS	ns2.foo.com.
...etc

ns1 and ns2.foo.com can run any nameserver they want, without being forced
to use any bind specific hacks.

> Second question - for delegations of /24 and above, what is the
> recommended/proper way to perform the delegation to another name
> server?

Just like the above, but then 1 level less-deep:

0.0.10.in-addr.arpa	IN NS nameserver1.ducks.quack.com



Oh, do read the RFC, as I did not, but this is probably just another correct
way of doing the same :P

Kai
-- 
begin 600 .signature