I have a server with hostmania.net and it was just recently moved to a new data center, so I edited all my DNS entries for the new ip I was given (My DNS is through zoneedit.com).

It appears that something has changed on the server settings and emails are not being sent to all members. I think the domain is wrong. It used to use the domain of evom.evolutionm.net, but now it uses localhost.localdomain... why is that? This appears to be the problem as some servers cannot resolve this domain. Can anyone explain how I may correct this? I'm including a copy of a returned email in case that helps:

Date: Fri, 8 Nov 2002 12:39:01 -0500
From: Mail Delivery Subsystem <MAILER-DAEMON@localhost.localdomain>
To: apache@localhost.localdomain
Subject: Returned mail: see transcript for details
Parts/Attachments:
1 Shown 12 lines Text
2 Shown 286 bytes Message, "Delivery Status"
3 Shown 1.1 KB Message, "Reply to post 'RMR Has a New Front Lip'"
3.1 Shown 20 lines Text
----------------------------------------

The original message was received at Fri, 8 Nov 2002 12:39:00 -0500
from apache@localhost

----- The following addresses had permanent fatal errors -----
<USER_EMAIL_REMOVED>
(reason: 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE)

----- Transcript of session follows -----
... while talking to mailin-04.mx.aol.com.:
>>> MAIL From:<apache@localhost.localdomain>
<<< 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE
554 5.0.0 Service unavailable

[ Part 2: "Delivery Status" ]

Reporting-MTA: dns; localhost.localdomain
Arrival-Date: Fri, 8 Nov 2002 12:39:00 -0500

Final-Recipient: RFC822; <USER_EMAIL_REMOVED>
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE
Last-Attempt-Date: Fri, 8 Nov 2002 12:39:01 -0500

Thanks,

Mark

Hi - some mail servers refuse to talk to other mail servers that do not have reverse DNS setup correctly, rDNS is where the domain name is looked up from an IP address. I assume that before you moved your rDNS was set up correctly and everything worked o.k. but it certainly is *not* now.

Try 'dig -x 64.83.120.242' and you will not get an domain name returned.

Your hosting tech support will be the ones to contact and ask them to configure your rDNS, when that is done see if you are still getting the problems - probably not.

HTH

YB

Here's the results I got from running dig:

; <<>> DiG 9.2.0 <<>> -x 64.83.120.242
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40668
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;242.120.83.64.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
120.83.64.in-addr.arpa. 37822 IN SOA ns1.wholesalebandwidth.com. root.wholesalebandwidth.com. 1035350438 10800 3600 604800 286

;; Query time: 33 msec
;; SERVER: 216.52.184.227#53(216.52.184.227)
;; WHEN: Fri Nov 8 14:34:05 2002
;; MSG SIZE rcvd: 111

So this problem stems from my host and they're the ones that need to resolve this? Is there anything I need to tell them so they understand the problem?

Thanks,

Mark

Hi - so that you can recognise when your rDNS is configured...

when you run the dig command again you should get a line 'similar' too....

;; ANSWER SECTION:
203.50.67.209.in-addr.arpa. 600 IN PTR futuresite.register.com.

.... and yes just ask your hosting provider to configure rDNS for your server and tell them the IP address and server name.
HTH

YB