Community Discussions and Support
Error connecting to primary server

I am seeing a problem processing email to some domains very recently.  I'll get Error connecting to primary server x.x.x.x.   When I resolve the domain name in nslookup on the same pc it shows the ip as y.y.y.y.  What the heck!?

I am seeing a problem processing email to some domains very recently.  I'll get Error connecting to primary server x.x.x.x.   When I resolve the domain name in nslookup on the same pc it shows the ip as y.y.y.y.  What the heck!?

[quote user="mwsasser"]

I am seeing a problem processing email to some domains very recently.  I'll get Error connecting to primary server x.x.x.x.   When I resolve the domain name in nslookup on the same pc it shows the ip as y.y.y.y.  What the heck!?

Have you entered the IP address(es) of the DNS host(s) in the MercuryE setup?

 

[/quote]

<p>[quote user="mwsasser"]</p><blockquote>I am seeing a problem processing email to some domains very recently.  I'll get Error connecting to primary server x.x.x.x.   When I resolve the domain name in nslookup on the same pc it shows the ip as y.y.y.y.  What the heck!?</blockquote><p>Have you entered the IP address(es) of the DNS host(s) in the MercuryE setup?</p><p> </p><p>[/quote]</p>

I'm confused.  Shouldn't MercuryE use the same dns as the pc?  It says it will use the same dns as listed in the windows networking if left blank.  I can see where it says 'resolved mx for domainname.org as x.x.x.x' but that ip is wrong.  Like I said, it should be y.y.y.y.  Further.. it says 'connection error during handshake.'

I'm confused.  Shouldn't MercuryE use the same dns as the pc?  It says it will use the same dns as listed in the windows networking if left blank.  I can see where it says 'resolved mx for domainname.org as x.x.x.x' but that ip is wrong.  Like I said, it should be y.y.y.y.  Further.. it says 'connection error during handshake.'

Some Windows configurations have problems with DNS resolving - it seems to be better to enter specific name servers into MercuryE.

Also, it's easier to help with DNS problems if you post full domain names rather than 'domainname.org'.

Some Windows configurations have problems with DNS resolving - it seems to be better to enter specific name servers into MercuryE. Also, it's easier to help with DNS problems if you post full domain names rather than 'domainname.org'.

How can this be, if the IP Address is already resolved in the logs with the correct IP-Address? If this is the point that causes the problem, there must be a bug, since the IP Adresses with the failed connections are resolved already.

 

 

<p>How can this be, if the IP Address is already resolved in the logs with the correct IP-Address? If this is the point that causes the problem, there must be a bug, since the IP Adresses with the failed connections are resolved already.</p><p> </p><p> </p>

Things like this can happen if the domain has incorrect MX records, for instance a numerical IP address instead of a hostname. It's very difficult to say though unless you give us real data to work with.

/Rolf 

<p>Things like this can happen if the domain has incorrect MX records, for instance a numerical IP address instead of a hostname. It's very difficult to say though unless you give us real data to work with.</p><p>/Rolf </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft