Re: bind9 graphical admin interface

[Craig Sanders <cas@taz.net.au>]

On Wed, Apr 02, 2008 at 08:30:14AM +1100, Craig Sanders wrote:
> if he has a portable netblock (i.e. he "owns" it directly, rather than
> it being owned by his upstream ISP and loaned to him) then he needs
> to contact whoever is responsible for IP address allocations in your
> country and ask for the .in-addr arpa domain to be delegated to his NS.
> 
> if it's a non-portable netblock owned by his upstream ISP then he needs
> to contact their tech people and ask the same.

BTW, note that the smallest net block that a .in-addr.arpa domain
can be delegated for is a /24.

if he has less than a /24 then there are ugly tricks that can be done
with CNAMEs, but they are complicated and a PITA and easy to screw up,
so he's extremely unlikely to ever get his upstream to bother. really,
it just isn't going to happen. he may, however, be able to get his
upstream to accept a regular text file listing his PTR records which
they can use to update the zonefile on their NS. i wouldn't hold my
breath waiting for this.

if he has more than a /24 or multiple /24s then he needs multiple
.in-addr.arpa domains delegated to his NS - one for each /24.

there's no way he'll have a /16 or a /8, which are the next sizes up
that can be delegated in one go.  it goes like this:

x.in-addr.arpa       /8   e.g. 192.in-addr.arpa
                          whoever owns that can delegate .in-addr.arpa
                          domains for the /16s & /24s within it.

x.x.in-addr.arpa     /16  e.g. 168.192.in-addr.arpa
                          whoever owns that can delegate .in-addr.arpa
                          domains for the /24s within it.

x.x.x.in-addr.arpa   /24  e.g. 0.168.192.in-addr.arpa

craig

-- 
craig sanders <cas@taz.net.au>

BOFH excuse #130:

new management