Date: Wed, 10 Sep 2008 18:07:18 -0600 From: Andrew Falanga <af300wsm@gmail.com> To: Patrick Mahan <mahan@mahan.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: mail server DNS configuration questions Message-ID: <48C86136.7040502@gmail.com> In-Reply-To: <48C6ADE7.8060608@mahan.org> References: <200809061928.28539.af300wsm@gmail.com> <48C6ADE7.8060608@mahan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Patrick Mahan wrote: > > > Andrew Falanga presented these words - circa 9/6/08 6:28 PM-> >> Hi, >> >> 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 72.24.23.252 "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) >> [/usr/home/andy] >> -> dig +short -t MX whitneybaptist.org >> 10 mail.whitneybaptist.org. >> [/usr/home/andy] >> -> dig +short -t A whitneybaptist.org >> 72.24.34.252 >> [/usr/home/andy] >> -> dig +short -x 72.24.34.252 >> 34-252.72-24-cpe.cableone.net. >> >> (from the church FBSD machine) >> [/home/afalanga] >> -> hostname >> whitbap >> [/home/afalanga] >> -> ifconfig fxp0 >> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> options=8<VLAN_MTU> >> inet 192.168.2.23 netmask 0xffffff00 broadcast 255.255.255.255 >> ether 00:d0:b7:74:87:48 >> media: Ethernet autoselect (100baseTX <full-duplex>) >> status: active >> [/home/afalanga] >> -> cat /etc/resolv.conf >> search McCutchanLAN >> nameserver 192.168.2.1 >> >> >> 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. >> > > > First, what are you trying to accomplish with the internal DNS? Make > it easier to > resolve machines in the 192.168.2.0 network? Allow lookups external > of the > 192.168.2.0 network? What machine is 'mail.whitneybaptist.com'? Is > it on the > 192.168.2.0 network? Is it reachable from the Internet? > > Who is the owner of whitneybaptist.org DNS zone? I show the following > NS servers: > > Patrick@widowmaker-~/src/MPS/DocDownload 140 > dig +short -t NS > whitneybaptist.org > ns1.domaindirect.com. > ns2.domaindirect.com. > ns3.domaindirect.com. > > Which is administered by tucows.com (Tucows, Inc) a seller of DNS > services. > >> 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? >> > > You can read the RFC's if you want, but you would be better served to > purchase > "DNS and BIND, Fourth Edition, by Paul Albitz & Cricket Liu" to learn > how to > administer DNS. > > Patrick It's been quite some time since I last looked at that book. It was at edition 3 then, and owned by the company I worked for so I didn't get to keep it. I'll have to look into it. Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48C86136.7040502>