Re: transfering vs. loading a zone

[Masataka Ohta <[e-mail]>]

W.C.A. Wijngaards wrote:

> Agree with Mark, that the server that loads the zone from text file (or
> whatever the first source) can refuse to send the zone through the
> ecosystem.  It can admit the zone, but then keep it as written by the 
> owner.

With AXFR/IXFR, that is an issue only with the primary nameservers.
Though RFC1034 does not disallow zone transfer with text files transferred
by ftp or e-mail, nameservers receiving text zone should be considered
the primary with regrad to AXFR/IXFR discussion.

The problem here, however, is that zone contents recognized valid
by the primary nameserver may be recognized invalid by secondary
nameservers.

Such inconsistencies are often caused by violent application of the
concept of "bailiwick" to glue As.

> | Hugh? If a name server tries to receive a new version of a zone and 
> fails,
> | it should continue to use an older version of the zone until it expires.
> 
> Yes.

And, we hope zone administrators take care of inconsistencies between
nameservers before or, in practice hopefully, immediately after the
zone expiration.

							Masataka Ohta



--
to unsubscribe send a message to [e-mail] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>