Esoteric network setup question

[William Palfreman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 30 Apr 2003, Bill Moran wrote:

> inbox wrote:
> > I have a hopefully not silly question;
> >
> > When I'm setting up my network, does it matter if I give the domain a
> > TLD or not?  Say I call my home network "myzoo".  I don't ever plan on
> > registering "myzoo.org" as a domain, and I don't ever plan on connecting
> > to my home network from the outside (TOS of my ISP forbids servers
> > anyways).  Should I call it "myzoo.org" or just "myzoo" in the network
> > configuration dialog or does it matter?  Do any programs expect a TLD
> > for the local domain?  The only reason I ask is every example in every
> > book I've seen has a TLD in the domain name, usually .com.
>
> I don't know of anything that would cause you to _need_ the TLD in the
> domain name.  You can probably get away without it.  Hell, I've run
> machines with _no_ hostname with success (although apps seem to be getting
> fussier about that and it doesn't seem to work any more).

I have found that fetchmail and sendmail reject mail in the form
<username at tld>, where tld is a top level domain resolvable using the
correctly configured LAN (primary master) nameserver, with a correct MX
record.  Personally I consider this a bug, but I haven't got round to
identifying exactly where it occurs.  Since then I've switched to using
the form host.lan.domain.tld, largely because I'm planning to setup
legitimate IPv6 DNS for them.  Anyway, I don't use the form hostname.tld
or username at tld anymore because of these issues.

- -- 
W. Palfreman. 			I'm looking for a job. Read my CV at:
Tel: 0771 355 0354		www.palfreman.com/william/cv-wfp2.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+sUdqlEOQDkvPqLYRArDQAJ9MhopAF++3Q+vNCzaBU00iL2dB8gCfZfpQ
Bu2IJ1zrXWHncxqg8yHNdGA=
=Y5uJ
-----END PGP SIGNATURE-----