i have an account on the server that has its MX record forwarded to an external IP address where they run their own mail server. The client recieves email fine from all sources except for any account on that machine. This is a problem because all of our support emails are hosted on that machine, and we cannot send/recieve support issue emails. any idea what could be causing this?
doesnt seemed to have worked
I removed domain.com and www.domain.com from /etc/localdomains and then sent a test email out to the client. the email gets stuck in the mail que will the following error:
Message 17hXBP-0007uC-00 is not frozen
delivering message 17hXBP-0007uC-00
LOG: 0 MAIN
== [email protected] R=lookuphost defer (-1): host lookup did not complete
I removed domain.com and www.domain.com from /etc/localdomains and then sent a test email out to the client. the email gets stuck in the mail que will the following error:
Message 17hXBP-0007uC-00 is not frozen
delivering message 17hXBP-0007uC-00
LOG: 0 MAIN
== [email protected] R=lookuphost defer (-1): host lookup did not complete
i had an error in my named.conf. i fixed that and tried again and now the error i get back is...
all relevant MX records point to non-existent hosts:
it appears that the DNS operator for this domain has installed an invalid MX record with an IP address instead of a domain name on the right hand side
...this is true, the MX record for domain.com is an IP number. The machine is a w2k server running exchange. it doesn't have a domain assigned to it so i put the IP address in. Does that machine need a domain?
all relevant MX records point to non-existent hosts:
it appears that the DNS operator for this domain has installed an invalid MX record with an IP address instead of a domain name on the right hand side
...this is true, the MX record for domain.com is an IP number. The machine is a w2k server running exchange. it doesn't have a domain assigned to it so i put the IP address in. Does that machine need a domain?
Having the same problem...
Hi scoy,
I am getting the same error as follows:
[email protected]
all relevant MX records point to non-existent hosts:
it appears that the DNS operator for this domain has installed an invalid MX record with an IP address instead of a domain name on the right hand side.
Did you find a fix for this. That the sarasotabyclub.net domain name is hosted by another host and they may have it setup on an IP address instead of a domain. But that's bogus isn't it? It should work either way.
Please let me know...
Thanks in advance!
UPDATE.... I did find a fix for this. I added the following line to my /etc/exim.conf file toward the top and it works now:
######################################################################
# MAIN CONFIGURATION SETTINGS #
######################################################################
allow_mx_to_ip = true
Hi scoy,
I am getting the same error as follows:
[email protected]
all relevant MX records point to non-existent hosts:
it appears that the DNS operator for this domain has installed an invalid MX record with an IP address instead of a domain name on the right hand side.
Did you find a fix for this. That the sarasotabyclub.net domain name is hosted by another host and they may have it setup on an IP address instead of a domain. But that's bogus isn't it? It should work either way.
Please let me know...
Thanks in advance!
UPDATE.... I did find a fix for this. I added the following line to my /etc/exim.conf file toward the top and it works now:
######################################################################
# MAIN CONFIGURATION SETTINGS #
######################################################################
allow_mx_to_ip = true
Definitely not bogus.
An MX record must must MUST point to a hostname.... always. And that hostname has to be resolving to the nameserver in question where the MX is configured, or the MX will be meaningless and mail will go to a black hole with numerous evil rejection messages.
If you point an MX to &mail.domain.com&
( IN MX 10 mail.domain.com. )
Then make sure that later in the zone you specify where &mail.domain.com& goes, with an A or CNAME record....
An MX record must must MUST point to a hostname.... always. And that hostname has to be resolving to the nameserver in question where the MX is configured, or the MX will be meaningless and mail will go to a black hole with numerous evil rejection messages.
If you point an MX to &mail.domain.com&
( IN MX 10 mail.domain.com. )
Then make sure that later in the zone you specify where &mail.domain.com& goes, with an A or CNAME record....