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. 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.
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.
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.
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.
Thanks,
Bret Van Horn
--------------------------------
Communi(k), Inc.
