Derek Martin <[EMAIL PROTECTED]> writes: > On Thu, Apr 14, 2005 at 09:20:43AM -0400, Paul Lussier wrote: > >> Case A: >> If you're just fooling around, and want to have a little network >> behind your firewall and have e-mail to/from family members on that >> network appear to be from some pseudo/make-believe domain which you >> haven't registered, yet you want mail outbound to the world to still >> work, it's a little complicated. > > It's not, really, as you yourself said later in the same post. Just > configure sendmail to masquerade as comcast.net, as you mentioned > before. Everything else is done as if you were using your own real > domain, with respect to inside hosts. Done. There's no DNS to set up > for outside hosts (i.e. you don't need MX records and such)... I > think this option is actually slightly simpler.
I guess what I meant by that, is it begins to get confusing to the human, especially if they're not the one who set all this up. The problem with using an entirely ficticious domain internally gets complicated if others within the network don't truly understand what's going on, and can't quite grok why when they send an e-mail with [EMAIL PROTECTED] the reply comes back to [EMAIL PROTECTED] And, when someone asks for their e-mail address, should they give out [EMAIL PROTECTED] or [EMAIL PROTECTED] In short, if you messing around with fictitious domains, and others are using your network, it's best not to tell them about it because you'll spend more time than it's worth trying to explain (and re-explain) it to them so they don't get confused. They'll still get confused, and really probably don't care :) > Host files are easy to configure, but hard to maintain. Every time > you add a host, you have to update the files on every existing system. > Still, if your network is going to stay small, you can avoid learning > about how to set up DNS if you'd rather not bother... That was my point. And since this was mainly about MTA configuration, I figured it best not to muddy the waters with DNS/DHCP configuration issues. > Do it yourself: If your ISP's name servers stop working, you don't > care. Yours keep working, as long as your connection to the Internet > keeps working. After the way ComCrap has been lately with their DNS, I'm about to set this up at home. I'm sick of my wife complaining she can't get out to the net all because some moron at ComCrap tripped over the extension cord and cycled power on their DNS server farm :) > The real down side of forwarding is that DNS search order breaks (this > might be fixed in BIND 9, but was definitely broken with BIND 4.x -- I > haven't tried it since then). > > Say you have this in your resolv.conf: > > search pizzashack.org example.com dancer.net > nameserver ns1.example.com > nameserver ns2.example.com Huh, I had forgotten all about that! I haven't checked to see if it's been fixed, but now that you mention it, I'm really curious :) -- Seeya, Paul _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
