Okay, sorry about sanitizing the names: domain1.com = www.communik.com
(207.170.212.4), domain2.com = cknewsletters.com (207.170.212.2)
mail.cknewsletters.com uses the .2 IP.
As for the MX records, here they are:
; <<>> DiG 2.0 <<>> mx cknewsletters.com
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 7
;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 2, Addit: 3
;; QUESTIONS:
;; cknewsletters.com, type = MX, class = IN
;; ANSWERS:
cknewsletters.com. 78612 MX 0 mail.cknewsletters.com.
;; AUTHORITY RECORDS:
cknewsletters.com. 78612 NS svr2.gstis.net.
cknewsletters.com. 78612 NS svr1.gstis.net.
;; ADDITIONAL RECORDS:
mail.cknewsletters.com. 78612 A 207.170.212.2
svr2.gstis.net. 10800 A 207.170.196.62
svr1.gstis.net. 10800 A 207.170.196.61
;; Sent 2 pkts, answer found in time: 9 msec
;; FROM: cobalt to SERVER: default -- 127.0.0.1
;; WHEN: Fri Apr 23 13:28:02 1999
;; MSG SIZE sent: 35 rcvd: 151
I hope this helps. :)
-Bret
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 24, 1999 3:21 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: MX, IPs and QMail
>
>
> On Fri, Apr 23, 1999 at 01:08:01PM +0100, Bret Van Horn wrote:
> >> Hello All-
> >>
> >> Okay, for starters, I'm relatively new to Unix administration (Solaris
> >> 2.6/sparc, more specifically) and Qmail, so please bear with
> me here. Be
> >> warned, verbose=on.
> >>
> >> The Setup:
> >> ------------
> >> We have a Solaris box, with www.domain1.com as the primary hostname,
> >set up
> >> with QMail. Tcpserver is not installed, in case that matters. We have a
> >> virtual domain pointed to that same box with its own IP, which we'll
> >call
> >> domain2.com.
>
> Why call it domain2.com? Why not call it what it is?
>
> >> That domain is listed in the control/virtualhosts and control/rcpthosts
> >> files. And yes, Qmail has been told to reload the virtualdomains and
> >> rcpthosts files. Our Solaris box came setup without a /etc/named.boot
> >file,
> >> if that matters, so we have no MX records on that machine (we're using
> >> /etc/hosts). Our ISP is taking care of setting up our MX records
> >upstream.
> >>
> >> The Problem:
> >> ------------
> >> When I send e-mail to domain2.com from our internal company network, it
> >> shows up just fine, with no problems. When I try to send mail to
> >domain2.com
> >> from outside of our network, nothing happens. No errors, nothing in the
> >> domain1.com logs and no bounces--until about a week later when I get a
> >> message from the external network's mail server saying it could not
> >connect
> >> to the host for domain2.com. Mail to domain1.com from outside our
> >network
> >> comes in just dandy.
>
> *Please* don't sanitize your DNS information by using fictitious domain
> names.
> If a DNS problem is the source of your troubles, there's no way anyone on
> the
> list can discover that.
>
> >> What I've found:
> >> ----------------
> >> After beginning to question whether our ISP had the proper MX records
> >set
> >> up, I discovered the wonderful Dig tool (yes, I am still learning the
> >> wonders of Unix!). A query on the MX records of domain2.com indicated
> >that
> >> they were forwarding all mail for domain2.com to
> mail.domain2.com, which
> >> they actually pointed (without telling us) to the domain2.com
> IP address
> >> *not* the domain1.com IP, which QMail was installed under. Still with
> >me? I
> >> tried adding mail.domain2.com to our locals file and rebooting ro no
> >avail.
>
> When you say "forwarding all mail for domain2.com to mail.domain2.com," do
> you
> mean that they have the MX record for domain2.com pointing to the machine
> mail.domain2.com? And what does "which they actually pointed (without
> telling
> us) to the domain2.com IP address" mean? This is where having real domain
> names
> would help. I suspect you've got a problem with CNAME records here, but
> without
> the real names I can't check.
>
> >> The Inevitable Newbie Questions:
> >> --------------------------------
> >> 1) Do they need to point mail.domain2.com to the IP of domain1.com for
> >qmail
> >> to catch the domain2.com mail? In other words, does QMail only listen
> >to the
> >> primary machine IP address? I have a sneaking suspicion this is the
> >case.
>
> That's definitely not the case--qmail doesn't listen to anything at all.
> You
> said you're not using tcpserver, so I assume you're using inetd, so it's
> inetd
> that's doing the listening. I don't know much about inetd, but I'd suspect
> that
> unless you told it to do otherwise it'll listen on all your interfaces.
>
> >> 2) If not, even though our ISP has MX records set up to forward the
> >> domain2.com e-mail to our domain1.com machine, do I still need to
> >create MX
> >> records on the domain1.com machine? This wasn't clear to me in the FAQ.
> >>
> >> 3) Is there anything else I may be overlooking that could be causing
> >this?
> >>
> >> I would really appreciate any help or suggestions you all might be able
> >to
> >> provide.
>
> Provide the real names of your domains, and someone will be able to tell
> you
> within seconds whether things are correct or need fixing.
>
> Chris
>
>
> --- Internet Message Header Follows ---
> Received: from muncher.math.uic.edu (131.193.178.181)
> by communik.com (FirstClass Mail Server v5.11)
> transient id 116; 1:22:39 PM -0700
> Received: (qmail 8576 invoked by uid 1002); 23 Apr 1999 20:21:15 -0000
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Precedence: bulk
> Delivered-To: mailing list [EMAIL PROTECTED]
> Received: (qmail 21362 invoked from network); 23 Apr 1999 20:21:15 -0000
> Received: from shemp.palomine.net ([EMAIL PROTECTED])
> by muncher.math.uic.edu with SMTP; 23 Apr 1999 20:21:15 -0000
> Received: (qmail 25764 invoked by uid 1000); 23 Apr 1999 20:21:29 -0000
> Date: Fri, 23 Apr 1999 16:21:29 -0400
> From: Chris Johnson <[EMAIL PROTECTED]>
> To: Bret Van Horn <[EMAIL PROTECTED]>
> Cc: Qmail List <[EMAIL PROTECTED]>
> Subject: Re: MX, IPs and QMail
> Message-ID: <[EMAIL PROTECTED]>
> References: <000701be8d81$eefa9610$0e06a8c0@bret>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 0.95.4i
> In-Reply-To: <000701be8d81$eefa9610$0e06a8c0@bret>; from Bret Van Horn on
> Fri, Apr 23, 1999 at 01:08:01PM +0100
>
