Hmm indeed! On Mon, Mar 17, 2008 at 4:13 PM, Mike Barnard <[EMAIL PROTECTED]> wrote: > hmmm > > > > > and it'll be up to CFI to do that. > > > > > > > > > no, you aren't wrong, however, since one can axfr from ns.ripe.net, > > ns.icann.org and demon.mtn.co.ug (at least over the weekend), then CFI > > hasn't explicitly told these server operators to deny axfr. They > > should have IMHO (and I think yours), but seems they haven't. > > > > > > > > > > I thought it was best practice to make sure that you as a secondary do not > leak records out. It should not be up to CFI to chase you down, although it > does lie on them to ensure that the .ug name servers and their secondaries > are well configured. >
it is pretty much BCP, but only if that's what the primary wants. Here is what I asked RIPE staff: > If ns-ug.ripe.net denies axfr for the .ug zone, then why shoudn't ns.ripe.net? > > Shouldn't the same policy apply to both ns's? > and their reply: Ah, I think I understand a bit more about what you mean. A long time ago all the TLD's were hosted on ns.ripe.net, after a while it was decided to move all the TLD to their own server where each TLD gets its own name e.g. ns-ug.ripe.net People from the TLDs were contacted to change to the new address, but some never replied or something else weird happened. At any rate, if you know anyone at .ug please tell them to contact us so that we can turn of the secondary on ns.ripe.net and move to ns-ug.ripe.net ---------------------------- I am thinking that something "wierd" happened recently. Anyway, Charles knows about it now, so it'll be sorted, one hopes. But maybe not now that I think about it, since Noah was @ CFI AND MTN (presumably he configged demon), perhaps it's possible that .ug don't care to deny axfr?? -- Cheers, McTim $ whois -h whois.afrinic.net mctim _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
