Domain Names — Concepts and Facilities¶
Mockapetris, P. (1987). Domain Names — Concepts and Facilities.
Cited by¶
4 citations across 4 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Client Server Model
- The many initiating consumers are the browsers, numerous and transient, carrying little persistent state and not needing to know one another. Initiation asymmetry: the browser opens the connection and sends a request; the server responds but never contacts a particular browser uninvited, except through mechanisms the client opted into (long-polling, server-sent events — the callbacks of the model). Addressability asymmetry: the browser must locate the server by URL, resolved through DNS, whereas the server need not know any browser in advance and discovers one only when it connects.
This sourceSpecifies DNS — resolving a name to an addressable server, the canonical locate-then-request discovery service.
- The many initiating consumers are the browsers, numerous and transient, carrying little persistent state and not needing to know one another. Initiation asymmetry: the browser opens the connection and sends a request; the server responds but never contacts a particular browser uninvited, except through mechanisms the client opted into (long-polling, server-sent events — the callbacks of the model). Addressability asymmetry: the browser must locate the server by URL, resolved through DNS, whereas the server need not know any browser in advance and discovers one only when it connects.
- Eventual Consistency
- Name resolution — hierarchical time-bounded propagation of name-to-address mappings, where an update is eventually seen by all resolvers as caches expire and refetch.
This sourceDefines the DNS hierarchy and TTL-bounded caching, so a record change propagates to all resolvers as caches expire and refetch — eventual consistency of name-to-address mappings.
- Name resolution — hierarchical time-bounded propagation of name-to-address mappings, where an update is eventually seen by all resolvers as caches expire and refetch.
- Registry-Mediated Discovery
- DNS: domain names resolve to current IP addresses; browsers and mail clients hold names and resolve at use, while web servers change IPs without consumer reconfiguration.
This sourceDefines DNS as a distributed registry resolving stable domain names to current addresses, with TTL-based caching (staleness).
- DNS: domain names resolve to current IP addresses; browsers and mail clients hold names and resolve at use, while web servers change IPs without consumer reconfiguration.
- Alias-to-Authority Mapping
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
Registry ID ref:c133608b74db · see in the full table