On Tue, 2004-10-05 at 13:57, Paul Howarth wrote:
> The easiest solution then is just to configure your nameserver to be a
> master for the ourdomain.com domain, and include machine.ourdomain.com
> as an A record in the zone in addition to all the entries you have on
> the "official" nameservers. Your LAN clients will get back answers from
> your nameserver (which knows about machine.ourdomain.com) and the rest
> of the Internet will get back answers from the official nameservers
> (which won't recognise machine.ourdomain.com). Just be sure to keep your
> private version of the zone in sync with the official one when you make
> changes.
Yeah, that's what most people do. But the key problem is that
"fred.ourdomain.com" isn't really "fred.ourdomain.com". The
.com/.net/etc TLDs aren't really a logical part of the 'real world' and
this will cause sendmail, et al, to be more difficult to install, no?
--
------------------------------------------------------------------------
Brian FahrlÃnder Christian, Conservative, and Technomad
Evansville, IN http://www.fahrlander.net
ICQ 5119262
AIM: WheelDweller
------------------------------------------------------------------------
Attachment:
signature.asc
Description: This is a digitally signed message part
