DNS was created because a single shared host-name file could no longer keep pace with a growing network. Before DNS, computers already used names: they looked them up in HOSTS.TXT, a centrally maintained file mapping host names to numeric addresses. DNS replaced that increasingly difficult distribution model with a hierarchical namespace and information maintained across many name servers.
What did computers use before DNS?
They used HOSTS.TXT. The Network Information Center (NIC) maintained the file of host-name-to-address mappings, and hosts retrieved it using FTP. People did not simply have to memorize numeric addresses: the file already let them use names instead.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
That arrangement worked while the network was small, but it concentrated both the directory and the work of publishing changes in one place. Local organizations could administer their own names and addresses, yet their changes would not become visible across the network until the NIC updated HOSTS.TXT. Organizations also wanted to structure names locally, and newer Internet applications needed a naming service that could describe more than host addresses. Paul Mockapetris’s 1987 account in RFC 1034 describes these pressures.
Why did the shared file stop scaling?
Every host that needed current mappings had to obtain a new version of the same file. As the number of hosts grew, distributing repeated complete copies became an increasingly costly way to publish even a small change. RFC 1034 states: “The total network bandwidth consumed in distributing a new version by this scheme is proportional to the square of the number of hosts in the network.” This is the 1987 specification’s description of the HOSTS.TXT distribution model, not a measurement of present-day DNS traffic.
#1 Best Overall
The bottleneck was administrative as well as technical. A central file meant local updates depended on a central publishing step. DNS addressed both problems by dividing responsibility: names were arranged hierarchically, and different portions of that namespace could be maintained by the organizations responsible for them.
What changed when DNS was introduced?
DNS made naming a distributed system rather than a single list that everyone had to retrieve in full. Its namespace is hierarchical: dots separate levels, and the hierarchy can roughly reflect organizational boundaries. Name servers hold information for different parts of the namespace, while resolvers find the information a user’s program requests.
The goal was broader than translating host names into addresses. RFC 1034 describes a consistent namespace for referring to resources, without building network identifiers, addresses, or routes into the names themselves. DNS also supports different types of information associated with a name, allowing the system to serve multiple applications.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA name can therefore remain useful even when an address changes with connectivity or network topology. The name-to-address mapping still has to be updated, but people and applications need not rely on a numeric address as the enduring identity. RFC 3467, an informational historical analysis published in 2003, also notes that a name could be associated with multiple addresses for different forms of connectivity: RFC 3467.
How does DNS find an IP address?
A program asks a local resolver for a particular kind of information associated with a domain name. The resolver contacts a name server it knows about. That server may provide the answer or refer the resolver to another server responsible for the relevant part of the namespace. The resolver can then return the result to the program.
- A program requests information. For example, it asks for an address associated with a name.
- A resolver seeks an answer. It queries a name server, which may answer directly or point it toward another server.
- The resolver follows what it needs. The precise route depends on the information already available and the responses received; every lookup does not necessarily start at the root or traverse every level.
- Answers can be cached. Resolvers and other DNS components can reuse cached data for a period, reducing repeated retrieval. Cached data is eventually discarded after its timeout.
As RFC 1035 explains, the resolver hides the distribution of data among name servers from the user. Redundant copies of information also help the system cope with server failures. The result is not one global phone book on one machine: it is a protocol and distributed database in which queries, referrals, redundancy, and caching work together. See RFC 1035 for the resolver and name-server design.
Rank #4
HOSTS.TXT and DNS: the key difference
| Question | HOSTS.TXT | DNS |
|---|---|---|
| Where was information administered? | The NIC maintained one central file. | Responsibility is distributed across the namespace and its name servers. |
| How did changes become visible? | Changes depended on the central file being updated and redistributed. | Responsible administrators maintain their portions of DNS data, which servers can provide to resolvers. |
| How did retrieval scale? | Hosts retrieved repeated complete versions of a shared file. | Resolvers request particular information, can follow referrals, and benefit from redundancy and caching. |
| What did names accomplish? | Names spared people from relying directly on numeric addresses. | Names retain that abstraction in a larger, hierarchical namespace, separate from network routes and addresses. |
Was there one exact year DNS was created?
There is no single creation moment established by these sources. RFC 1034 and RFC 1035, the core specifications by Paul Mockapetris, were published in November 1987. RFC 3467 describes DNS as having evolved during design and initial implementation, and notes that some historical reasons were not fully documented. It is more precise to say that the design was formalized in the 1987 specifications than to assign DNS one definitive invention or first-deployment date.
Recommended Free Tools
One further distinction matters: a “domain name” is not always being used in a DNS context. RFC 1034 cautions that the term appears in other contexts too. DNS is the naming system and protocol that organizes and retrieves its own distributed data; the words “domain name” alone do not prove that a particular use involves DNS.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
