dns-wg

Download

dns-wg@ripe.net

May 2004

3 participants
1 discussions

reverse delegation of a /16 doesn't work with new interface
by Marc Pauls 17 May '04

17 May '04

Hello, trying to setup a reverse delegation for a /16 (where ns.ripe.net is required) through the new mnt-domains based interface at auto-dbm(a)ripe.net doesn't seem to work. After trying several times I decided to send the delegation mail to the old auto-inaddr(a)ripe.net and it worked fine. When creating a new delegation of a /16 I always thought that the mandatory ns.ripe.net becomes a delegated nameserver itself by passing it as one of the nserver: entries in the domain template. e.g: domain: 222.111.in-addr.arpa ... nserver: ns1.customer-ns nserver: ns2.customer-ns nserver: ns.ripe.net ... That always worked with auto-inaddr(a)ripe.net but doesn't with auto-dbm(a)ripe.net. The error messages given by the database: ***Warning: (related to ns2.coustomers-ns) The nameserver ns.ripe.net was found listed for the zone at ns2.comstomers-ns (10.10.10.10), but was not one of the delegated nameservers (ns2.customers-ns, ns1.customers-ns). Only the delegated nameservers should be listed anywhere for the zone. ***Warning: (related to set) Only 2 delegated nameserver(s) ns2.customers-ns, ns1.customers-ns. There should be at least 3. ***Warning: (related to set) The RIPE NCC nameserver exactly one was not present in the list of delegated nameservers for this zone (ns.ripe.net). This is required by the RIPE NCC for this type/size of zone. Of course the NS-entries in the zones are all okay and contain ns.ripe.net of course... how I wrote... with auto-inaddr(a)ripe.net it worked. All in all that means that ns.ripe.net doesn't become authorative itself by passing it to a new /16 delegation through the new interface and so the database returns error messages. kind regards, Marc.

3 2

Results per page: