Re: Bind 9 AXFR Modification vs AXFR Clarification

[Mark.Andrews@isc.org]

> Mark.Andrews@isc.org writes:
> > Whenever you have a parent and child zones under different administrative
> > controls it is impossible to change both zones simultaniously.
> 
> False.
> 
> Set the clocks correctly, and schedule the change on all the servers for
> a particular time, using (for example) the tinydns timestamp feature
> described in http://cr.yp.to/djbdns/tinydns-data.html. When that time
> rolls around, all the servers will change their data simultaneously, as
> RFC 1034 requires.

	So now you want to extend the protocol so that each record has
	an inception time and a expiration time.  We could create a
	new transfer protocol to do this and treat this data as meta
	data.

	However you would still have the problem of the meta data
	being inconsitant.  You would still need to ensure that it
	is transmitted in the right order or that servers didn't
	modify it while it was being transmitted or that you ban
	any server but the master server sending copies of the zone.

	The problems are inherent with having different source maintaining
	copies of the same data.
	
	Mark

> Yes, this is difficult to achieve with BIND, AXFR, etc. But it's easy to
> achieve with better software, better replication protocols, etc. You're
> making a fool of yourself when you call it ``impossible.''
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org