RE: [dns-wg] Secondary service on ns.ripe.net for reverse delegations.
-
To: "'Brett Carr'" brettcarr@localhost, dns-wg@localhost
-
From: Jørgen Hovland jorgen@localhost
-
Date: Mon, 14 May 2007 11:20:07 +0200
Hi,
I hope this does not become mandatory, only optionally or discontinue it.
A very few amount of LIRs would have to send a zonefile in the size of (2^96 ) * 32 * 4 * 20 bytes to ns.ripe.net if it becomes mandatory.
I take it for granted that RIPE (in addition to the LIR) does not have the bandwidth or the harddrive capacity for these zones.
Additionally, such a requirement would limit the amount of supported RRs and degrading competitive (dis)advantages.
Example 1:
These LIRs run software that updates any record/zone instant on all nameservers at once (milliseconds) when the customer performs changes. I am unsure if this is possible with RIPEs nameserver (NOTIFY probably limited to SOA changes etc).
j
-----Original Message-----
From: dns-wg-admin@localhost [ ] On Behalf Of Brett Carr
Sent: 14. mai 2007 10:21
Subject: [dns-wg] Secondary service on ns.ripe.net for reverse delegations.
As mentioned in my presentation at RIPE 54 last week we have become
aware that there is an inconsistency between ipv4 and ipv6 with
regard to obtaining reverse delegation.
The reverse delegation procedure listed at http://www.ripe.net/rs/
reverse/reverse_howto.html has the following listed:
-----snip
Secondary Service by the RIPE NCC
For IPv4: If your zone is a /16 reverse zone, you will need
to set up ns.ripe.net as a secondary server
For IPv6: If your zone is a /32 reverse zone, you may use
ns.ripe.net as a secondary
-----snip
We think it would be a good idea to address this inconsistency, this
could be done in several ways including but not limted to:
Make ns.ripe.net mandatory on ipv4 and ipv6 delegations
Make ns.ripe.net optional on ipv4 and ipv6 delegations
Discontinue the secondary service on ns.ripe.net for new delegations.
Our suggestion and preference would be to make ns.ripe.net optional
on both ipv4 and ipv6 delegations.
We would welcome and encourage input from the dns community on this
subject.
Regards
Brett
--
Brett Carr
Manager -- DNS Services Group
RIPE Network Coordination Centre
Amsterdam
|