[nflug] Re: nflug Digest, Vol 29, Issue 25

[Cyber Source]

That should be fine. Just edit your account at dyndns so the mx record 
points to the IP that your assigning to that box. Edit your router NAT 
translation for that public IP you'll have to the internal IP and port 
forward 25, 110 and 143 at least to the box. Edit your hostname on the 
box. I don't know how dnydns handle it's records, I have used it only 
for dynamic hosting but it's probably pretty simple. We run our own DNS 
here, if you need help with that later, let me know.

Andrew Long wrote:
> The public side is static. I'll be assigning an IP from our corporate
> block and setting up the NAT in a PIX 506. Since it's testing only at
> this point, I plan on using my own DYNDNS domain name and setting up
> the DNS records there.
>
> I figure I need the following:
> domain.com.  NS  NS1.domain.com
> NS1.domain.com  A  123.456.78.9
> domain.com  MX  mail.domain.com
> mail.domain.com  A 123.456.78.9
>
> Does that make sense? Records for hosted domains would be held on
> NS1.domain.com.
>
> - Andrew
>
> On Feb 17, 2008 12:00 PM,  <nflug-request at nflug.org> wrote:
>   
>> Send nflug mailing list submissions to
>>         nflug at nflug.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://www.nflug.org/mailman/listinfo/nflug
>> or, via email, send a message with subject or body 'help' to
>>         nflug-request at nflug.org
>>
>> You can reach the person managing the list at
>>         nflug-owner at nflug.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of nflug digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: testing mailserver & bind (Cyber Source)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 17 Feb 2008 10:44:18 -0500
>> From: Cyber Source <peter at thecybersource.com>
>> Subject: Re: [nflug] testing mailserver & bind
>> To: nflug at nflug.org
>> Message-ID: <47B85652.9050303 at thecybersource.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Ok, sorry it took so long.
>>   First things first.
>> Is your current connection for you network dhcp or static on the public
>> side and is there any dns currently pointing to this location or in use
>> at this location?
>>
>> Andrew Long wrote:
>>     
>>> I'd like to set up a test mailserver on our network. Eventually, the
>>> purpose would be to handle the mail for our domain which is now farmed
>>> out. My confusion comes in setting up the DNS (bind) and on the right
>>> configuration for the hostname and interfaces, etc.
>>>
>>> My confusion probably arises from not having a firm grasp of DNS and
>>> common practices in setting up public services within private lan
>>> segments (using the Cisco PIX to route requests).
>>>
>>> I tried to come up with a specific question, but, if there are folks
>>> with with experience here, I'd just like to start a dialog and try to
>>> learn something...
>>>
>>> I have built several severs for our company, postfix, freeradius, and
>>> I always manage to muck my way through, but I could use the input of
>>> anyone with experience in this area...
>>>
>>> On a side note... Is there any intention of this group having any
>>> meetings on the LAN segment? IE in a physical location.
>>>
>>> Regards,
>>>
>>> Andrew
>>> _______________________________________________
>>> nflug mailing list
>>> nflug at nflug.org
>>> http://www.nflug.org/mailman/listinfo/nflug
>>>
>>>       
>> ------------------------------
>>
>> _______________________________________________
>> nflug mailing list
>> nflug at nflug.org
>> http://www.nflug.org/mailman/listinfo/nflug
>>
>>
>> End of nflug Digest, Vol 29, Issue 25
>> *************************************
>>
>>     
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>