Connected: An Internet Encyclopedia
RFC 1035 - 6.1.1. Control

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1035
Up: 6. NAME SERVER IMPLEMENTATION
Up: 6.1. Architecture
Prev: 6.1. Architecture
Next: 6.1.2. Database

### 6.1.1. Control

A name server must employ multiple concurrent activities, whether they are implemented as separate tasks in the host's OS or multiplexing inside a single name server program. It is simply not acceptable for a name server to block the service of UDP requests while it waits for TCP data for refreshing or query activities. Similarly, a name server should not attempt to provide recursive service without processing such requests in parallel, though it may choose to serialize requests from a single client, or to regard identical requests from the same client as duplicates. A name server should not substantially delay requests while it reloads a zone from master files or while it incorporates a newly refreshed zone into its database.

Next: 6.1.2. Database

Connected: An Internet Encyclopedia
RFC 1035 - 6.1.1. Control