Connected: An Internet Encyclopedia
RFC 1035 - 5.2. Use of master files to define zones

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1035
Up: 5. MASTER FILES
Prev: 5.1. Format
Next: 5.3. Master file example

### 5.2. Use of master files to define zones

When a master file is used to load a zone, the operation should be suppressed if any errors are encountered in the master file. The rationale for this is that a single error can have widespread consequences. For example, suppose that the RRs defining a delegation have syntax errors; then the server will return authoritative name errors for all names in the subzone (except in the case where the subzone is also present on the server).

Several other validity checks that should be performed in addition to insuring that the file is syntactically correct:

1. All RRs in the file should have the same class.

2. Exactly one SOA RR should be present at the top of the zone.

3. If delegations are present and glue information is required, it should be present.

4. Information present outside of the authoritative nodes in the zone should be glue information, rather than the result of an origin or similar error.

Next: 5.3. Master file example

Connected: An Internet Encyclopedia
RFC 1035 - 5.2. Use of master files to define zones