diff --git a/network.pdf b/network.pdf
index 20eaa62125d267ee827fe076d55921b268576a00..20c05cecc97c24c458735e3a7a6a0db91c079c60 100644
Binary files a/network.pdf and b/network.pdf differ
diff --git a/network.txt b/network.txt
index 0582bb31d8d7f68028cd5117a32f416967d40e9e..be2e4f5533ff92f53f2a20604638cd44b9706a3d 100644
--- a/network.txt
+++ b/network.txt
@@ -251,3 +251,39 @@ flag. The way `traceroute` works is that it sends a small packet with
 a very small TTL flag, and waits to see the ICMP Time Exceeded
 message, the sender of which is TTL hops away. Note that this is not
 reliable, as paths can vary from packet to packet.
+
+
+Finding Other Hosts
+-------------------
+
+Your simplest go-to for looking up a host's IP address given its name
+is to use the `host` command:
+
+    host gizmonic.cs.umd.edu
+
+On older systems, you would use
+
+    nslookup gizmonic.cs.umd.edu
+
+This has been deprecated on newer systems, so you should always use
+`host` when available. If you want more detail about the query and
+response, you can use `dig` instead:
+
+    dig gizmonic.cs.umd.edu
+
+All of these have a number of options available to you to control what
+kinds of queries you perform. They are also able to perform *reverse
+lookups*. That is, given an IP address, they will tell you the
+(canonical) hostname:
+
+    host 128.8.130.3
+    dig -x 128.8.130.3
+
+You can also find out who registered a domain with `whois`:
+
+    whois umd.edu
+
+You can even find out who owns the subnet an address is in:
+
+    whois 128.8.130.3
+