[db-wg] Since when does one need 3 nameservers for inverse?
- Previous message (by thread): [db-wg] mirroring connections with Whois Database enabled
- Next message (by thread): [db-wg] Since when does one need 3 nameservers for inverse?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ulrich Schmid
schmid at switch.ch
Mon Mar 27 15:00:50 CEST 2006
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). Regards Ulrich Schmid
- Previous message (by thread): [db-wg] mirroring connections with Whois Database enabled
- Next message (by thread): [db-wg] Since when does one need 3 nameservers for inverse?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]