DNS presentation outline
Phillip Hunter
hunter@owlriver.com
Copyright (c) 2000 Owl River Company

Presentation to Central OH Linux Users Group
   May 31, 2000


I.	Why DNS ?
	- convenience
	- NOT authentication or security
	- alternatives:  YP/NIS, flat files

II.	External resolution
	- The remote site knows more than you (hopefully)
	about which hosts it wants you to use, and what
	their IP addresses are, at the moment.
		(Demo - view aol.com MX records)
		(Demo - view www.cnn.com web servers)
	- MX records
	- 'Round-robin' websites, and load balancing

III.	Internal resolution
	- consider a simple common 'hosts' file
		(Demo - view sample hosts file)
	- supported in all unices (SCO is wierd)
	and even in the pre-W'2000 Windows products

IV.	Lightweight tools
	- root server cache
		- cachebuild tool

	- local (internal) resolution
		- h2n
			(Demo -   h2n -H ./hosts -d inside.net \
				-m 5:stones.wcbe.org -n 172.16.34 )

V.	No good GPL'd unified scripts.
	Why? - very complex variations possible

=======================================
We have mangled /etc/named.conf, /etc/resolv.conf, and installed
bind for purposes of this demo ... we'll de-install after demo.


FILES:
========================================

ORCnamed_build
boot.cacheonly

cachebuild
cachebuild.awk
cachebuild1.2.tar.gz

db.127.0.0
db.172.16.34
db.cache
db.inside

dnsoutline.txt

h2n
h2n.man

hosts

named.boot
named.conf
named.conf.ORIG