Search Again:

Re: Mail Exchange Problems

From: John Duncan
Date: Thursday, July 3, 1997
Time: 2:08:00 am

At 4:00 PM -0400 7/2/97, Charles Lai wrote:
>----------------------------------------------------------------------
>
>Subject: Mail Exchange problems
>From: <ctlai@ix.netcom.com>
>Date: Fri, 20 Jun 97 10:30:57 -0700
>
>We have tried to get the DNS and Electronic mail on our system to work,
>but we are having problems. I am able to send a message from a domain
><reeftank.com>, but I am not able to send a message to the domain or
>access it. The return message when I try to send mail to the domain is:
>
> ----- The following addresses had permanent fatal errors -----
><webman@reeftank.com>
>
> ----- Transcript of session follows -----
>550 <webman@reeftank.com>... Host unknown (Name server: reeftank.com: no
>data known)
>
>
>When I try to access mail from the domain, the message I get is:
>
>Execution of Schedule "Connect Now" at Fri, Jun 20, 1997 8:00:12 AM
>Connecting To Internet using Account "webman@reeftank.com"
> Checking for mail
> ** Could not resolve the domain name "reeftank.com" because this
> domain name does not exist.
>
>QuickDNS Pro and EIMS 1.1.2 are both on the same machine. QuickDNS Pro is =
>
>the primary name server for the domain name <reeftank>. Any suggestions
>or examples would be much appreciated. The interesting thing is that the
>DNS appears to be working for the HomeDoor redirect extension so that
>when one types in http://www.reeftank.com, one is redirected to
>http//www2.reeftank.com/reeftank/.
>

I had the exact same symptoms with EIMS 1.1.2 and QDNS-Pro running on a
Quadra-630 with MacTCP. I solved the problem by changing the primary DNS
reference in MacTCP on that machine to refer to a different DNS than itself.

QDNS Tech Support also identified a problem with the target email domain
where the MX record was a CNAME to a CNAME to an Address, but the reverse
lookup of the Address did not confirm the "A" record name. They thought
changing the MX record to point directly to the address in the A record and
fixing the in-addr.arpa reference to have the same name would have resolved
it without changing the MacTCP DNS reference.

John Duncan (duncanj@jedtech.com)
JEDtech Consulting
http://www.jedtech.com



Messages In This Thread:



Return to Digital Point Solutions' Home Page