At 12:41 AM +0200 2004-09-18, Fernando Garcia wrote:
I was not only thinking about DNS but all the other servers that must be migrated AND this document should not be BIND centered (though the examples use bind). I'm not sure about how the DNS server for Windows work, but let me be a little suspicious.
Fair enough.
The problem in your phrase is "network administrator ensures.. Outgoing packets are routed via the appropiate provider", this usually means "source routing" (I can paint many scenarios with this meaning), a not so simple task and the person -network administrator- that will use this document (I hope) is not a very qualified technician, if she/he is qualified, she/he wouldn't need this document.
The issue is that there's not really anything we can do to fix this problem. If their administrators are not minimally competent, there is nothing that you can do with any written document that can help, and indeed you are likely to make a bad situation worse by overwhelming them with procedures and policies that they are unlikely to understand. I think the principle needs to be kept as simple as possible, and the resulting document should be kept as short as possible.
I think you have the problem of multiple changes at the registrar no matter what.
Its a problem, so the less changes, the better. Do you agree with this statement?
Changes should be kept to a minimum, yes. However, I don't think we can assume that the Registrar will automatically screw up everything, every time. Simple sets of changes should be no problem, even if they need to be done more than once. If we assumed that the Registrar would screw up everything, every time, then the entire DNS would collapse. -- Brad Knowles, <brad@stop.mail-abuse.org> "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See <http://www.sage.org/> for more info.