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] Re: rev delegation robot and selection of NS to pull zone from
- Previous message (by thread): [dns-wg] Re: rev delegation robot and selection of NS to pull zone from
- Next message (by thread): [dns-wg] Re: rev delegation robot and selection of NS to pull zone from
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Thu Nov 20 21:26:34 CET 2008
On Thu, Nov 20, 2008 at 08:14:34PM +0100, Anand Buddhdev wrote: > The configuration you describe above isn't illegal. However, the RIPE > NCC's provisioning system won't be able to cope with it. Currently, > there's no way to explicitly provide a list of master servers that zone > transfers should be attempted from. > > One solution is to list a server in the MNAME field which will provide > zone transfers. Alternatively, you can choose not to use ns.ripe.net as while the latter is probably the most pragmatic approach, it could interfere with other requirements. Depending on how widespread this issue is, the WG might also consider to propose a new attribute for the domain: object to denominate the (list of) AXFR source(s). -Peter
- Previous message (by thread): [dns-wg] Re: rev delegation robot and selection of NS to pull zone from
- Next message (by thread): [dns-wg] Re: rev delegation robot and selection of NS to pull zone from
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]