The Article That Built a Career
A five-page DNS tutorial written by a young developer in India. Later archived by the UK's national security body, held in the British Library, and referenced in university curriculum. This is where 25 years of technical writing began.
Published: February 16, 2001 · BIND 4.9.x · UNIXI have been writing about technology for 25 years. But every journey has a first step — and mine was a tutorial published on DomainNotes.com, part of the internet.com publishing network, on February 16, 2001.
The article was called “Setting Up DNS Servers.”
I was a software professional working in India at the time, fascinated by how the internet actually worked under the hood. I wrote what I knew. I published it. And then I moved on.
What I didn’t know was what happened next.
Where This Article Ended Up#
Over the years, without my knowledge, the article found its way into places I never imagined.
What I Contributed to DNS Education#
"In 2001, setting up a DNS server was a gatekept skill. This article made it reproducible for anyone with a UNIX box and a text editor."
To understand why this article mattered, you need to understand 2001. There was no Stack Overflow. No DigitalOcean tutorials. No AWS Route 53. DNS was the invisible foundation of the entire internet — and documentation was scarce. O’Reilly’s DNS and BIND book was essentially the only comprehensive resource, and it cost money.
in-addr.arpa reverse mapping — critical for mail servers, as reverse DNS was already becoming an anti-spam verification check in 2001.The Internet in February 2001#
BIND was the internet. In 2001, BIND (Berkeley Internet Name Domain) powered the vast majority of DNS servers on the internet. Every website, every email server, every hostname resolution depended on BIND configurations exactly like the ones in this article. A mistake in your SOA serial number meant your DNS changes wouldn't propagate. A missing reverse DNS record meant your mail server got blacklisted.
This wasn't academic knowledge. This was the plumbing of the internet — and getting it wrong had real consequences.
The Original Article — Restored#
Every word below is exactly as published on February 16, 2001, on DomainNotes.com (internet.com network). Reconstructed from the Internet Archive snapshot.
The Basics#
The core of domain name system (DNS) is the invention of a hierarchical, domain-based naming scheme and a distributed database system for implementing this scheme. This allows local control of segments of the overall database, yet the data is available across the entire network through a client-server scheme. This database of domains is maintained by interNIC (Network Information Center). Robustness and adequate performance are achieved through replication and caching.
A program called name server constitutes the server half of DNS’s client-server mechanism. Name servers contain information about some segment of the database and make it available to clients called resolvers. Resolvers are just library routines that create queries and send them across a network to a name server.
Conceptually, the Internet is divided into several hundred top-level domains where each domain covers many hosts. The top-level domains come in two flavors: generic and countries. The generic domains are com (commercial), edu (education), mil (military), int (international), org (organization), net (network providers). The country domains include one entry for each country.
The whole database is pictured as an inverted tree with root node at the top. Each node is a basic top-level domain and each top-level domain has many nodes. For example the com node may have child nodes as abc and abc may have a child node bhavin (a sub domain of abc.com) and so on. Thus we can say that each node is also a root of a new sub tree of the overall tree. Thus when we want to access bhavin we type http://bhavin.abc.com in our browsers.
Need of DNS File#
Originally, all domain name resolution occurred on one computer, which contained a text file called HOSTS.TXT. However, as time went on, the HOSTS.TXT file required update after update. The computer containing this file was also being overrun with name resolution requests. Managing millions of constantly changing sets of names became a serious problem, so each domain that is registered now has its own DNS file.
DNS Resolution Process — Interactive#
http://bhavin.abc.com in your browser. It needs an IP address to connect.Resource Records (RR)#
Each domain, whether it is a single host or a top-level domain, can have a set of resource records associated with it. For a single host, the most common record is just its IP address, but many other kinds of resource records also exist. When a resolver gives a domain name to DNS, what it gets back are resource records associated with that name. So the real function of DNS is to map domain names onto the resource records.
| # | Code | Name | Function |
|---|---|---|---|
| 1 | A | Network Address | Stores host name and IP address. Used to translate host names to IP addresses. |
| 2 | NS | Authoritative Name Server | Identifies the name servers in the domain. |
| 3 | MD | Mail Destination | Now replaced by MX. |
| 4 | MF | Mail Forwarder | Now replaced by MX. |
| 5 | CNAME | Canonical Name | Stores aliases for hosts in the domain. |
| 6 | SOA | Start Of Authority | Required for every domain. Stores DNS information for the domain. |
| 7 | MB | Mailbox Domain Name | |
| 8 | MG | Mailbox Member | |
| 9 | MR | Mail Rename Domain | |
| 10 | NULL | Null Resource Record | |
| 11 | WKS | Well-known Service | Stores information about network services from hosts in the domain. |
| 12 | PTR | Pointer to a Domain Name | Used to translate IP addresses into host names. |
| 13 | HINFO | Host Information | Stores hardware information for specific hosts. |
| 14 | MINFO | Mailbox Information | |
| 15 | MX | Mail Exchange | Stores information about where mail for the domain should be delivered. |
| 16 | TXT | Text String | Stores up to 256 characters of text per line. |
| 17 | RP | Responsible Person | Stores information about the person responsible for the domain. |
| 18 | AFSDB | AFS-type Services | |
| 19 | X.25 | X.25 Address | |
| 20 | ISDN | ISDN Address | |
| 21 | RT | Route Through |
Configuring a UNIX DNS Server#
Configuring a DNS server requires several files and databases to be modified or created. The process is time-consuming, but luckily has to be done only once for each server. If you intend on using the package called BIND (the Berkeley Internet Name Domain), then you should be sure that you get version 4.9.x.
Animated Terminal — Watch the Config Build#
The 5 BIND Configuration Files — Interactive Tabs#
Click each file tab to explore the configuration that powered DNS in 2001.
named daemon where to find everything. If this file exists, DNS starts. This is the entry point for the entire server.; named.boot directory /usr/lib/named primary abc.com named.hosts primary 25.143.in-addr.arpa named.rev primary 0.0.127.in-addr.arpa named.local cache . named.ca
; named.hosts file
; Start of Authority RR
abc.com. IN SOA bhavin.abc.com. root.bhavin.abc.com. (
2 ; Serial number
7200 ; Refresh (2 hrs)
3600 ; Retry (1 hr)
151200 ; Expire (1 week)
86400 ) ; Min TTL
; Name Service RRs
abc.com IN NS bhavin.abc.com
subnet1.abc.com IN NS jack.subnet1.abc.com
; Address RRs
sumi IN A 143.23.25.7
bhavin IN A 143.23.25.9
mary IN A 143.23.25.12
jay IN A 143.23.25.23
solly IN A 143.23.25.43
pepper IN A 143.23.25.72
in-addr.arpa. Critical for mail servers — reverse DNS was already becoming an anti-spam check in 2001.; named.rev file
23.143.in-addr.arpa IN SOA bhavin.abc.com. root.bhavin.abc.com. (
2 ; Serial number
7200 ; Refresh (2 hrs)
3600 ; Retry (1 hr)
151200 ; Expire (1 week)
86400 ) ; Min TTL
; Name Service RRs
23.143.in-addr.arpa IN NS bhavin.abc.com
100.23.143.in-addr.arpa IN NS jack.subnet1.abc.com
; Address RRs
7.25.23.143.in-addr.arpa IN PTR sumi
9.25.23.143.in-addr.arpa IN PTR bhavin
12.25.23.143.in-addr.arpa IN PTR mary
23.25.23.143.in-addr.arpa IN PTR jay
43.25.23.143.in-addr.arpa IN PTR solly
72.25.23.143.in-addr.arpa IN PTR pepper
localhost resolves correctly. Short and essential.; named.local
0.0.127.in-addr.arpa IN SOA bhavin.abc.com. root.bhavin.abc.com. (
2 ; Serial
7200 ; Refresh
3600 ; Retry
151200 ; Expire
86400 ) ; Min TTL
1.0.0.127.in-addr.arpa IN PTR localhost.
ns.internic.net at 198.41.0.4 was the starting point for resolving any domain on Earth.; named.ca ; servers for root domain . 99999999 IN NS ns.internic.net; servers by address ns.internic.net 99999999 IN A 198.41.0.4
Deep Dive — Expandable Sections#
Click each section to expand the original 2001 explanation.
Once these files are configured you have set up your own DNS server.
DNS Then and Now: What Changed#
| Aspect | 2001 (This Article) | 2026 (Today) |
|---|---|---|
| DNS Software | BIND 4.9.x on bare-metal UNIX | BIND 9, CoreDNS, Knot, PowerDNS, cloud-managed |
| Configuration | Hand-edited text files (named.boot, named.hosts) | APIs, Terraform, web dashboards |
| Hosting | Your own physical server | AWS Route 53, Cloudflare, Google Cloud DNS |
| Security | None (DNS was implicitly trusted) | DNSSEC, DoH, DoT, DNS-over-QUIC |
| Record Types | 21 (documented in this article) | 80+ (AAAA, SRV, DNSKEY, TLSA, CAA, SVCB, HTTPS...) |
| Root Servers | 13 physical machines | 13 identities, 1,700+ anycast instances |
| Learning | Scarce tutorials, O'Reilly books, tribal knowledge | Stack Overflow, DigitalOcean, YouTube, AI assistants |
| TLDs | ~250 (generic + country) | ~1,500+ (including .dev, .app, .ai...) |
The fundamentals in this 2001 article are still correct. DNS is still a hierarchical, distributed database. The inverted tree still describes the namespace. SOA records still have the same five fields. Reverse DNS still uses in-addr.arpa. The resolver still sends UDP packets to a name server. Twenty-five years of evolution in tooling, security, and scale — but the architecture I described in 2001 remains the foundation of every domain name lookup on Earth.
The 25-Year Arc#
"Setting Up DNS Servers" — DomainNotes.com / internet.com
First published article. Archived by UKCERT, held in the British Library, referenced by Texas A&M University. Written on a dial-up era network, published before Stack Overflow, Wikipedia, or cloud computing existed.
Drupal 6 Panels Cookbook — Packt Publishing
First published book. Reviewed on Slashdot, announced on Drupal.org, listed on Google Books, Amazon.com, and Amazon.co.uk. From tutorials to technical books.
The AI Advantage — Co-authored
Enterprise AI strategy. From DNS plumbing to AI transformation — the throughline is making complex technology accessible and actionable.
bhagavad.net, AEORank, vinpatel.com
Open-source AI projects, technical writing, and 25 years of building in public. The discipline of writing clearly about a technical topic — established in that first DNS article — has never changed.
Why I’m Sharing This Now#
"Every expert was once a beginner. This is the article that made me one."
Authenticity matters more than ever in an age of AI-generated content. This article exists. It was written by a human. It was validated by institutions. The Wayback Machine timestamp does not lie.
Show your early work. The technology industry has a short memory. We celebrate the new and forget the foundational. This article was written before most of today’s AI tools, cloud platforms, or modern frameworks existed. It was written with a text editor and published on a dial-up era network.
If you are a young professional reading this — write what you know. Publish it. You have no idea where it will end up. A tutorial I wrote as a young professional in India ended up in the British Library. Not because I submitted it, but because someone else decided it was worth keeping.
That is the standard I have tried to hold myself to ever since.
Verification & Sources#
All archival claims in this post are independently verifiable:
| Institution | Evidence | Link |
|---|---|---|
| Internet Archive | Article archived June 27, 2003 | View archive |
| UKCERT | Listed in tutorial repository | ukcert.org.uk |
| British Library | Held in national collection | bl.uk |
| Packt Publishing | Drupal 6 Panels Cookbook (2010) | Amazon |
Bhavin “Vin” Patel has been writing about technology since 2001. From DNS servers to AI pipelines — the throughline is making the complex accessible. Find him at vinpatel.com.