[email protected] wrote:
> I only mentioned mydomain.com as an example, my real 
> domain used was something else :).

Yes I understand. What I mean is to use example.com as an example 
domain, instead of mydomain.com or something. It will prevent confusion 
and is very helpful. For example, anyone would be able to see that you 
use an example and obfuscated your real domain.

There is this story about how the owner of the noreply.com (or similarly 
named) domain received a lot of confidential email because companies 
incorrectly used that domain name as a noreply address.

Similarly you wouldn't like spammers to harvest your supposed example 
email addresses such as [email protected] and abuse it. What if it is 
a valid address used by someone? Etcetera...

> So it should look like this
> 
> assp.box.com     IN  A     192.168.1.1
> mydomain.com     IN  MX 10 assp.box.com.
> 
> smtp.server.com  IN A     192.168.1.2
> 192.168.1.2      IN PTR   smtp.server.com.
> mydomain.com     IN A     192.168.1.2

Your example is rather unreadable since you use existing domains and how 
am I supposed to know you do or do not own box.com and server.com. And 
if you don't you're (ab)using someone else's domains. ;-)

With regards to externally reachable services an entry would look 
something like this:

;
; BIND data file for example.com
;
$TTL    86400
@       86400   IN      SOA     example.com. root.example.com. (
                                 20081007        ; Serial
                                 604800          ; Refresh
                                 86400           ; Retry
                                 2419200         ; Expire
                                 604800 )        ; Default TTL

         IN      NS      ns1.example.com.
        IN      MX      10      assp.example.com.

example.com.            IN A    333.333.333.333
assp                    IN A    333.333.333.333
smtp                    IN A    333.333.333.333
ns1                     IN A    333.333.333.333

It doesn't matter much if there is a firewall in between, the server 
itself doesn't have to have the external IP. The firewall then has IP 
333.333.333.333 and routes traffic to specific ports such 25 and 587 to 
the proper internal server(s). In fact that's how I have it set up at home.

You would ideally want to have a reverse dns entry resolving 
333.333.333.333 to smtp.example.com if smtp.example.com is the server 
which recipients see email coming from. Normally your ISP takes care of 
reverse dns, unless you have a corporate account, I would think. If so 
you can ask them to add the reverse dns entry.

Greetings,
Jeroen

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to