On 2/28/2012 9:18 PM, John Hudak wrote:
> Ahhh, the crux of my cluelessness:
> Stan Hoeppner <s...@hardwarefreak.com> wrote:
> "Any dyndns service that allows using a real domain.tld will work. Make
> sure
> your consumer router is doing dynamic IP updates to the dyndns provider.
> Create an MX record with the FQDN of your mail host. Since dyndns
> services provide wildard resolution, you do not create an A record for
> the MX host, just the MX record. "
>
> So, I dont understand...some specifics: I have a server:
> machine 1 is named by me: m1.homeunix.org (192.168.1.10)
> user on machine 1 is: stan, so email to stan is s...@m1.homeunix.org
You need to "unthink" the DynDNS.org way of doing things.
And you're probably not really wanting to route mail to individual
machines with local mailboxes, as you state above. Nobody has done that
for a decade or so.
> DynDns (the service) offers managed DNS service and lets you pick from a
> list of domain names. I chose server1.homeunix.org (I gave my machines
> names with .homeunix.org..don't know if this was wrong or right???)
Again, get DynDNS out of your mind.
> I want to map the outside name, server1.homeunix.org (whatever IP address
> DynDNS assigned to it) to my 'inside name' m1.homeunix.org (my assignment
> is 192.168.1.10)
> Someone in the outside world wants to send an email:
> s...@server1.homeunix.org) and I want to make sure it is routed to:
> (effectively, s...@m1.homeunix.org).
> What do I put in the MX record? What do I put in main.cf?
Using TZO as an example, simply because I'm familiar with it, you'd do
the following:
1. Sign up for an account
2. Configure your broadband router to send dyndns updates to TZO
(instructions on their site). If your current router can't do it,
$20 buys you one that can.
3. Register your domain, e.g. johnhudak.com, at a cheap registrar
such as godaddy.com.
4. Create an MX record in your TZO control panel: mail.johnhudak.com
It will automatically associate the IP address
5. Configure your router to port forward WAN TCP 25 to the IP of
your Postfix box.
6. Configure the Linux hostname as mail in /etc/hostname.
7. Configure Postfix with:
myhostname = mail.johnhudak.com
myorigin = johnhudak.com
mydestination = johnhudak.com
(all 3 aren't required, read the Postfix docs)
Follow the previous instructions I posted for outbound relaying through
your ISP submission servers.
> Thanks for the pointer to TZO.
IIRC, dyndns.org offers similar capability with one of their paid
services, but for less money than TZO. However, I've found that users
trying to switch from dyndns free service to the pay service, and who
have no knowledge/education WRT "normal" DNS and SMTP, etc, have a
really hard time migrating, as the free dyndns.org concept of domains
clouds their minds. Switching from free dyndns.org to TZO tends to help
folks clear the free "dyndns way" and digest other concepts on how
things are done.
The best solution by far is to get a static IP from your ISP so you can
avoid most of the nonsense above. I pay an extra $120/year for the
static IP and it's worth every penny, 33 cents/day actually. So to host
my own SOHO mail server 'correctly' including my domain registration and
DNS service, I'm paying an extra 53 cents/day above and beyond the cost
of the standard 10Mb/s DSL package, which is 99 cents/day.
--
Stan
> On Tue, Feb 28, 2012 at 6:55 PM, Stan Hoeppner <s...@hardwarefreak.com>wrote:
>
>> On 2/28/2012 11:08 AM, John Hudak wrote:
>>> I can sympathise as I looked into doing this first with sendmail and more
>>> recently with postfix. Unfortunately after spending lots of time
>> reading,
>>> I could not put the pieces together the right way to run a home server.
>> My
>>> circumstances were similar to yours - multiple machines on a 198.162.x.x
>>> network, trying DynDns, etc. Some things I did along the way that
>> helped:
>>> Installed DD-wrt on my wireless router that gave me better control over
>>> network operation, such as assigning static addresses to all my machines,
>>> allowed automatic updates of my DynDns IP address, etc.
>>>
>>> My most pressing need was to have outbound service, the capability to
>> send
>>> updates from some of my servers to my gmail and work accounts, as well as
>>> send received faxes from my fax server. I found a nice program called
>>> Simple SMTP (ssmtp) that did exactly what I wanted and took all of 10 min
>>> to install, configure, and test. It may be of some value to you.
>>>
>>> While I would dearly love the inbound mail service capability (very
>> helpful
>>> for me to use my email to fax gateway), the outbound only service
>> suffices
>>> for the time being.
>>>
>>> I looked high and low for some sort of help/how-to and did not find one.
>>> If you succeed, I'd be very interested in how you set up postfix.
>>
>> Worth reading:
>> http://www.hardwarefreak.com/postfix-adsl-relay-config.txt
>> That covers the Postfix outbound setup so your mail isn't blocked by
>> everyone due to dynamic IP status. This relays mail through your ISP,
>> just as you would with Thunderbird, Outlook, etc.
>>
>> The inbound setup simply requires something like TZO dynamic DNS
>> service, which I used for many years and it worked flawlessly. Any
>> dyndns service that allows using a real domain.tld will work. Make sure
>> your consumer router is doing dynamic IP updates to the dyndns provider.
>> Create an MX record with the FQDN of your mail host. Since dyndns
>> services provide wildard resolution, you do not create an A record for
>> the MX host, just the MX record. Make sure your router is port
>> forwarding TCP 25 from the WAN interface to the RFC1918 address of your
>> Postfix server, and that's about it.
>>
>> --
>> Stan
>>
>>
>>
>
