mail server DNS configuration questions
af300wsm at gmail.com
Sun Sep 7 01:29:56 UTC 2008
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 188.8.131.52 "lot's of networks"
Private Network <--> CableOne <--> Internet
Now, our mail server's IP is 192.168.2.23. 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 whitneybaptist.org
-> dig +short -t A whitneybaptist.org
-> dig +short -x 184.108.40.206
(from the church FBSD machine)
-> ifconfig fxp0
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.2.23 netmask 0xffffff00 broadcast 255.255.255.255
media: Ethernet autoselect (100baseTX <full-duplex>)
-> cat /etc/resolv.conf
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
192.168.2.0/24 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:
internal.whitneybaptist.org 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?
More information about the freebsd-questions