Connected: An Internet Encyclopedia
RFC 1035 - 6.3. Zone refresh and reload processing

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1035
Prev: 6.2. Standard query processing
Next: 6.4. Inverse queries (Optional)

### 6.3. Zone refresh and reload processing

In spite of a server's best efforts, it may be unable to load zone data from a master file due to syntax errors, etc., or be unable to refresh a zone within the its expiration parameter. In this case, the name server should answer queries as if it were not supposed to possess the zone.

If a master is sending a zone out via AXFR, and a new version is created during the transfer, the master should continue to send the old version if possible. In any case, it should never send part of one version and part of another. If completion is not possible, the master should reset the connection on which the zone transfer is taking place.

Next: 6.4. Inverse queries (Optional)

Connected: An Internet Encyclopedia
RFC 1035 - 6.3. Zone refresh and reload processing