neale/homepage
neale
/
homepage
1
0
Fork 0
Code Pull Requests Actions Activity

Fix typos in DNS document

This commit is contained in:
Neale Pickett 2009-11-11 00:20:05 -06:00
parent b572dcda41
commit 4694e806c7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
papers/DNS.mdwn
View File

@ -1,4 +1,4 @@
[[!meta title="How DNS Works"]] Title: How DNS Works
When you request a URL like `http://goob.woozle.org/~neale/foo.html`, When you request a URL like `http://goob.woozle.org/~neale/foo.html`,
the first thing your browser does is send out a DNS query on the first thing your browser does is send out a DNS query on
@ -23,9 +23,9 @@ The reason the .org domain said to go to 216.39.146.229 is because
that's what I listed as the primary authoritative name server for the that's what I listed as the primary authoritative name server for the
"woozle.org" domain with my host registrar (pacificroot.com). A lot of "woozle.org" domain with my host registrar (pacificroot.com). A lot of
people use networksolutions.com as their host registrar. So on people use networksolutions.com as their host registrar. So on
216.39.146.229, I have an authoritative name server (nsd) that knows 216.39.146.229, I have an authoritative name server that knows about the
about the woozle.org domain. Some other authoritative name servers are woozle.org domain. Some examples of authoritative name server software
tinydns and BIND (the Buggy Internet Name Daemon). are nsd, tinydns, and BIND.
Your recursive resolver has now obtained the mapping from Your recursive resolver has now obtained the mapping from
"goob.woozle.org" to 216.39.146.229, so it returns that IP address to "goob.woozle.org" to 216.39.146.229, so it returns that IP address to