[db-wg] Since when does one need 3 nameservers for inverse?

On Mon, 27 Mar 2006, Ulrich Schmid wrote:

>
> on 8.2.2006 11:10 Uhr Brett Carr wrote:
> >> -----Original Message-----
> >> From: db-wg-admin at ripe.net On Behalf Of Hank Nussbacher
> >> Sent: Wednesday, February 08, 2006 10:19 AM
> >> Cc: rdns-project at ripe.net
> >> Subject: [db-wg] Since when does one need 3 nameservers for inverse?
> >>
> >> In the "Reverse Delegation How To":
> >> http://www.ripe.net/rs/reverse/reverse_howto.html
> >> it states:
> >>
> >> "NS Servers
> >> Ensure you have at least two nameservers that are
> >> authoritative for the zone. The resolvable names of these NS
> >> servers should be in the NS resource records of the zone. The
> >> nameservers should be on different subnets."
> >>
> >> Yet when I submit a request I get:
> >> ***RDNS:    (related to set) ERROR (20 points): At least 3 nameservers
> >>              are required for each properly delegated zone.
> >> We found only
> >>              2 in your submission.
> >>
> >> In addition the reverse delegation checker at:
> >> http://www.ripe.net/cgi-bin/delcheck/delcheck2.cgi
> >> doesn't flag only 2 nameservers as an error.
> >>
> >> What gives?
> >>
> >
> > Indeed you are right, something doesn't look quite right here. Thanks for
> > flagging it I'll take a look.
> >
> > Brett
> >
>
> Any news about this item?
> Changes to the domain objects are still rejected by the delegation
> checker due to the (wrong) requirement of 3 nameservers and this
> prevents us to perform simple updates (e.g. contact address changes).


My apologies, we answered Hank directly but I don't think the relevant
information made it back to the db-wg.

If you are requesting/updating a /16 the requirement for 3 nameservers is
correct, the 3 comprising of 2 nameservers of your own and the mandatory
inclusion of ns.ripe.net.
We identified a problem in the wording of the error message that the
delegation checker provides and this is being updated by our software
engineering department so that the exact problem will be more obvious to
users.

Hope that helps.

--
Brett Carr                              Ripe Network Coordination Centre
System Engineer -- Operations Group     Singel 258 Amsterdam NL
http://www.ripe.net                     +31 627 546046
GPG Key fingerprint = F20D B2A7 C91D E370 44CF  F244 B6A1 EF48 E743 F7D8