Moin! On 21.11.2008, at 10:28, Wilfried Woeber, UniVie/ACOnet wrote:
My feeling is that the current behaviour is quite reasonable. Of course we might suggest to look at the NS records (in addition maybe), but I presume that many folks do not allow zone transfers from *all* NS in the set. Correct, but only one is required for a proper transfer.
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.
Both are options, but I still would like to know if it wouldn't make more sense to use nserver records or NS RRset. Do you have some statistics on how often the MNAME is not in the nserver/NS RRset?
I definitely don't have any figures. Sorry that was a question to Anand, but I didn't point that out. Anand do you have statistics for the current delegations?
So long -Ralf --- Ralf Weber Platform Infrastructure Manager Colt Telecom GmbH Herriotstrasse 4 60528 Frankfurt Germany DDI: +49 (0)69 56606 2780 Internal OneDial: 8 491 2780 Fax: +49 (0)69 56606 6280 Email: rw@colt.net http://www.colt.net/ Data | Voice | Managed Services Schütze Deine Umwelt | Erst denken, dann drucken ***************************************** COLT Telecom GmbH, Herriotstraße 4, 60528 Frankfurt/Main, Deutschland * Tel +49 (0)69 56606 0 * Fax +49 (0)69 56606 2222 * Geschäftsführer: Albertus Marinus Oosterom (Vors.), Rita Thies * Amtsgericht Frankfurt/Main HRB 46123 * USt.-IdNr. DE 197 498 400