Hi all,
One customer complains that mails from the website to users are being bounced by a lot of ISP’s.
Bounce message: < win22.m****here.biz #5.5.0 smtp;553 We do not accept mail from IP addresses without reverse DNS. See Reverse DNS lookup - Wikipedia >
The webapplication currently does not support external smtp mail services, so question is can rdns be implemented for the new IP-space at WACO? Customer claims that before migration no rdns errors occured.
the old IP was 204.14.108.1, and you can do a lookup and see, and I can look in the rejected mail logs and see a lot rejected for it
SO, is it possible, yes, is it something we will do? I guess we can evaluate it and discuss a but, but no promises it will be done. A shame apps don’t support external mail
204.14.108.1 has a rDNS entry: mail.goodandready.info
Assume that this rDNS entry has there been a long time?
Why not list the new WACO IP space in rDNS?
Wikipedia says:
Internet official documents (RFC 1033, RFC 1912 Section 2.1) specify that “Every Internet-reachable host should have a name” and that such names match with a reverse pointer record.
So assume everybody likes to have rDNS for their environment. Of course you get the reseller-discussion, but with m****here and g******** domains I don’t see any real reseller complaints about it.
hrm, if that has rDNS it was there before we got the IP space, as we don’t directly control the rDNS on those ranges (which was always a problem since they would not delegate it to us we had to wait forever on them)
