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/[email protected]/
[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 ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Fri Nov 21 11:18:14 CET 2008
On Fri, Nov 21, 2008 at 11:05:25AM +0100, Ralf Weber wrote: > >Unless we find a "clever" way to provide the info about the name > >server(s) > >to try for a transfer, overall, we would just increase the number of > >failed > >attempts. Whether that would do any harm (at the NCC's or customer's > >end) > >is a different story, maybe. > Yes it could clutter the logs, but if one transfer would succeed it > would be ok. I have used this technique successfully during various > DNS migrations. So maybe the easiest idea is to change the structure of the nserver attribute to something like: nserver: name-of-ns-server [transfer] where "transfer" is optional parameter which is recognised by NCC? Regards, Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- 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 ]