This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] reverse delegation of a /16 doesn't work with new interface
- Previous message (by thread): [dns-wg] reverse delegation of a /16 doesn't work with new interface
- Next message (by thread): [dns-wg] reverse delegation of a /16 doesn't work with new interface
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at TechFak.Uni-Bielefeld.DE
Sun May 16 00:31:09 CEST 2004
Hello, setup of ns.ripe.net is supposed to work by sending the domain template to auto-dbm, as long as certain preconditions are met. See for example slide 12 of Olaf's presentation http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-dns-rdns-update.pdf > ***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. It is difficult, if not impossible, to track down a specific problem if the details come in disguise. In this case it would be interesting to see the SOA RR of the zone in question. -Peter
- Previous message (by thread): [dns-wg] reverse delegation of a /16 doesn't work with new interface
- Next message (by thread): [dns-wg] reverse delegation of a /16 doesn't work with new interface
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]