If you don't have any private names for your computers. You don't
need to run DNS. We have 6 computers on our home LAN, only the
gateway machine has a public IP address and name. The rest have only
private names (bearhouse.lan as you can by looking at the message ID).
There is a small amount of mail between machines, most of it warning
of errors that need to be fixed. Without explicit entries in
/etc/postfix/transport for each private name, mail didn't go thru.
Also the gateway machine has two names, one private, one public (thru
dyndns.org). The private name is permanent. The public name may go
away if I move and can't have a always on connection or my IP address
changes frequently. Without a DNS server, Postfix requires I use the
public name.
It basically comes down to the fact that I spent less time setting up
a private, caching DNS server than I spent trying to get around not
having one.
If you have only one machine, this isn't a problem.
Jeffrey
Quoting Praise
Which ever package you choose, be prepared to spend a fair amount of time on it. If you have a single computer with an always on Internet connection and it has a real Internet name and IP address (no private LAN names, no masquerading). It is relatively simple. If you have a private LAN domain (i.e., domain and host names that are only in /etc/hosts and are not resolvable from the Internet), set up a DNS server first. It will make life much easier.
HTH, Jeffrey
I have a real name, and some MX records pointing to my pc already. I have taken it from www.dtdns.net Do I have any advantage to set up a real DNS before it? (That one will come later, though).
Praise
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck