Need Help Understanding "Reverse DNS Lookup" AOL Comcast Bullshit
 

I just now noticed that all of the e-mails I send from my server to Comcast and AOL users come back. Which sucks, because my parents use Comcast and several people in my family use AOL.

The mails come back because the IP dosent resolve back to the domain the mail was sent from. Somebody's half-baked idea of an anti-spam measure. The best way to get rid of spam is to kill all the goddamn mother fucking spammers, not block my LEGIT MAIL because I havent implemented some stupid ponzi scheme on my server. Stupid fucking idea if I have ever heard of one. If I was allowed by ARIN to have every domain have its own FUCKING IP then that would be just fine, but I am not and I really dont want to pay my ISP for that many IPs either.

I called AOL's postmaster department and yelled at them for a while because I was angry and because it felt good and because AOL sucks and they deserve it anyway. They wouldnt budge. So I finally decided I would buy enough additional IPs for my main domains that I send mail from and make them resolve to those domains. So I bought the IPs and told the guy who handles all the "linux shit" which I am not good at to set it up. He said it cannot be done because something to do with the way my NOC has my IPs setup? Something about "delegating authority" or some stupid bullshit. What the fuck?

Is he stupid or is there truth to this? What would my ISP have to do with getting an IP to resolve to a domain when a server does a lookup on it? Isnt that a server side issue exclusively? When he asked me if I have ever had a problem with this, I said no. He thought that was funny, told me I have been living under a rock because this has been going on forever, etc, etc. Oh well, maybe so. But I dont

So in the mean time, a big FUCK YOU to AOL, Comcast and anyone and everyone else implementing this stupid fucking RFC. Fuck you, your family and everyone that uses you, I hope you all die (except for my family, I hope thier internet goes down and never comes back up) tommrow!

means you need to have your IP resolve to a domain just like your domain resolves to an IP :)

All you have to do is contact your host and tell them to change the ptr records for your outgoing smtp ip address (probably webserver ip unless you changed it) to something like server.$yourdomain.com and bam would be fixed.

Whoever runs your namservers (could be your host/ISP, could be you if you run your own DNS server, could be some third-party), just has to setup reverse DNS on your domain.

Basically all it does, is if you "nslookup xx.xx.xx.xx" it will give you your domain name, same as when you "nslookup domain.com" ti gives you your IP address.

It's quick and easy and there is no need for purchasing additional IP addresses.

Reverse DNS records have to be put in by whoever has official authority over the IP. It's most likely your host, or their NOC. Just send them a message and say you need reverse pointers set up for whatever IP, to resolve back to whatever domain you have on the server. They should know exactly what to do and can usually do it within a few minutes.

You don't need 1 ip for every domain. If you're on a shared IP, the IP address just needs a reverse pointer to a valid domain on the server.