Andrew Falanga wrote:

Well, my clients at church are still having issues and after working with George, a respondant to my original questions, I think that most, if not all, of my problems are related to DNS and how we've got it improperly configured.

First, a crude drawing of how our mail server exists in the world:

192.168.2.x/24       "lot's of networks"
Private Network <--> CableOne <--> Internet

Now, our mail server's IP is On the router, he (the person at whose house the mail server is) has IP forwarding setup so that mail get's sent to our FreeBSD machine. Using dig, here's the responses:

(from my FBSD machine at home, not the server)
-> dig +short -t MX
-> dig +short -t A
-> dig +short -x

(from the church FBSD machine)
-> hostname
-> ifconfig fxp0
        inet netmask 0xffffff00 broadcast
        ether 00:d0:b7:74:87:48
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
-> cat /etc/resolv.conf
search McCutchanLAN

It doesn't take a rocket scientist, or a computer scientist, to figure out we've got DNS issues. I'm thinking that I should setup a domain within the network on this box. I've done this before, at work. The question I've got is I've never actually integrated a domain like this to a domain on the Internet. I'm thinking that we'll setup something like: with hosts in that sub-domain.

So, what would my DNS tables need to look like to make this happen. Also, to any knowledgable souls here, what RFCs address these issues?


Andy, I'm not sure I'm DNS guru enough to answer all your
questions, but --- you don't specify what "problems" are
being experienced at the location, and, are you certain it's
not about this?

[25] Sat 06.Sep.2008 21:58:25
Host not found: 3(NXDOMAIN)

*Not having* a reverse entry for a mail server is often
the cause of issues.

And the RFC for ESMTP is #2821.


Kevin Kinsey
In Denver it is unlawful to lend your vacuum cleaner to your next-door
_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to