PRE-RESOLUTION BASICS
	Verify that /etc/resolv.conf points to the IP address assigned to dnscache, and, at least temporarily, only to that IP address. If not, edit /etc/resolv.conf until it points only to that IP address.
	Verify that named is not on, and not set to go on at next boot:
		ps ax | grep named
		/sbin/checkconfig | grep named
		: If named is on, shut it off with /etc/rc.d/init.d/named stop, or however
		: it's done on your distro. If named is set to go on at any boot level of
		: interest (1, 2, 3, 4, 5), set it off with the /sbin/chkconfig named off
		: command.
	Verify Internet Connectivity
		ping `head -n3  /service/dnscache/root/servers/@ | tail -n1`
		: Note: The first -n determines the line of the file to be ping'ed. If 3
		: doesn't work, try 2 and 1. If you're not connected, reconnect. Outside
		: DNS can't work until you have a connection. Frequently check this,
		: because dialup connections disconnect frequently.
	Verify that your djdns-centric alias is pingable
		ping IP address assigned to dnscache
		: If not pingable, fix it.
	Verify that /service is symlinked right
		ls -l /service
		total 0
		lrwxrwxrwx  1 root root 21 Jan  7 19:02 dnscache -> /var/service/dnscache/
		lrwxrwxrwx  1 root root 20 Jan  7 21:01 tinydns -> /var/service/tinydns/
		[slitt@mydesk djbdns]$
		: If the symlinks are wrong, redo the symlink step.
	Verify that svscan is running.
		ps ax | grep svscan
		: If it's not running, there's probably something wrong with your
		: daemontools or ucspi-tcp installation
	Verify that tinydns and dnscache are running
		svstat /service/dnscache
		svstat /service/tinydns
		: Both should say "up". If not, try to run them, and if they can't run,
		: figure why. Look at the logs, and see what happens when you try to bring
		: them up with svc -u /service/*
Verify forward caching DNS
	ping www.yahoo.com
		: If the ping command does not resolve, and if there's nothing
		: obvious, investigate the following:
		Internet connectivity
			: If you're on dialup or any kind of
			: temporary connection, verify that you're still online.
		Correct IP address
			cat /service/dnscache/env/IP
			: The preceding command should print the IP address in
			: /etc/resolv.conf -- the IP address you've assigned to the
			: dnscache service. If not, there was probably an error in your
			: installation.
		Correct IP address
			dir -l /service/dnscache/root/ip/*
			: If a file whose name is the IP address of the IP in
			: /etc/resolv.conf is not listed, create an empty file whose name is
			: that IP address. Use the touch command. Note that that same IP
			: address should be that of the network interface you're using for
			: dnscache. It will probably be either the NIC card IP address, or
			: an alias thereof.
		Check the log
			: Look at the /service/dnscache/log/main/current log.
Verify reverse caching DNS
	dig -x <IP address of www.yahoo.com>
	: This won't resolve to www.yahoo.com, but it should resolve to something.
	: If there's nothing in the answer section, there's something odd in your
	: dnscache installation, because dnscache has no separate configuration
	: for reverse resolution.
Verify forward authoritative DNS
	dig  @<IP you assigned to tinydns when installing djbdns> <fqdn of host on your subnet>
	: The preceding tests forward authoritative DNS without /etc/resolv.conf
	: and without the dnscache->tinydns link. If it does not resolve, check
	: the following:
		Reasonable data file
			less /service/tinydns/data
			File should have a dot or Z line for forward dns
			If it doesn't have a dot, it should have an & for forward DNS
			It should have = lines for each host on the subnet
			If you don't use = lines, 
				you should have + lines
Verify reverse authoritative DNS
	dig  @<IP you assigned to tinydns when installing djbdns> -x <IP address of host on your subnet>
	: The preceding tests reverse authoritative DNS without /etc/resolv.conf
	: and without the dnscache->tinydns link. If it does not resolve, check
	: the following:
		Reasonable data file
			less /service/tinydns/data
			File should have a dot or Z line for reverse dns
			If it doesn't have a dot, it should have an & for reverse DNS
			It should have = lines for each host on the subnet
			If you don't use = lines, 
				you should have ^ lines
					with properly configured in-addr.arpa addresses
Verify forward authoritative DNS through /etc/resolv.conf
	dig  <fqdn of host on your subnet>
	: If this doesn't work but forward DNS worked when you went around
	: /etc/resolv.conf and the dnscache->tinydns link, the problem has to be
	: in /etc/resolv.conf or the dnscache->tinydns link. Do the following:
	Investigate /etc/resolv.conf
		cat /etc/resolv.conf
		: Verify that the address you've bound dnscache to is in there. Note
		: that there may be occasions where you'll need the address bound to
		: tinydns, but usually it will be dnscache. If the correct IP address
		: is not in there, put it in.
	Investigate dnscache->tinydns link
		ls /service/dnscache/root/ip
		: If there is not a file whose name is the address in /resolv.conf is
		: not there, use touch to create an empty file whose name is that IP
		: address.
Verify reverse authoritative DNS through /etc/resolv.conf
	dig  <fqdn of host on your subnet>
	: If this doesn't work but reverse DNS worked when you went around
	: /etc/resolv.conf and the dnscache->tinydns link, and forward authorative
	: DNS through resolv.conf and the dnscache->tinydns link worked, there is
	: an odd problem. Verify that everything worked until this point, verify
	: that you're still connected.