[KLUG Members] LAN's and DNS

[Peter Buxton]

--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


Okay, so address 192.168.1.0/24, e.g., is "invisible" to the outside
world. Cool. But what about internal address NAMES? Since our ISP is the
NS for caresswm.org (the www. name and the MX records) and since I DON'T
want to serve as our own authoritative NS to the Real World(tm), what do
I do?=20

1. If I can set bind to go out to the ISP for unknown addresses, I can
   name all the machines thisandthat.caresswm.org and just leave
   www.caresswm.org undefined. Do I set myself as a slave of our ISP, or
   do I use the "hints" option?

2. Fictional names: I can just tell the machines they are in domain
   cares.lan, which is not unlike the 192 addresses in that they don't
   exist on the greater internet. Assuming my MTA knows to stamp mail
   with the proper domain (and it does), and I have no other services to
   the outside world (aside from AUTH), is this a good plan?

TIA

--=20
http://www.killdevil.org/~peter
but if we know anything about god,
god is *arbitrary*. -- bob dylan

--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9b3YUaAK8ZwqLoskRAoMxAJ9GnHWXm7z3/rgSdnrjZFeQ5cA+9gCfSsa3
6GEQjkxhf1tf5wBpzZCht8I=
=AVWV
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--