> -----Original Message----- > > I called aol.com and got the ball rolling to unblock me and > establish a feedback loop, but in the meantime, I think I had > better establish a reverse DNS zone for the server, just in > case that had a part in the complaints. My problem is that > I've got to be very careful about this since I cannot afford > any down time if I screw it up. > > I have DNS handled by ZoneEdit.com: > Domain: mollynet.com, 66.93.153.62 > My ISP is Speakeasy.net. > SpeakEasy is my ISP as well. All I had to do is put in a Support Ticket to have them add reverse DNS entries for my IP addresses. Reverse DNS is exactly as it is written - it is DNS in reverse. Forward DNS resolution is when a FQDN (www.google.com) is resolved to an IP address 216.239.57.99. Reverse DNS is when an IP address is queried for it's reverse DNS record. Basically, the owner/admin of the IP address range - of which you are a part - must create the reverse DNS entries. So, have SpeakEasy create a reverse DNS entry of mollynet.com (or mail.mollynet.com, etc) for 66.93.153.62 and you should be good to go. - John -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
