Just noticed that rDNS is not resolving on my server IP's. They are setup correctly in server command and have been for 3+ years. Mail is bouncing from some receiving mailservers due to not rDNS. This particular server is not in H1 either...

Anyone else having issues with rDNS on their server IP's?

Okay here on 207.44.232.x (H1-P2)

Thanks for checking. 2 of my 3 servers are not resolving rDNS even though they are configured correctly (and have been for some time) in server command. When I try to re-save the rDNS entry in server command I get the following error:

Can you PM me the ip address that your server is in so that we can investigate the issue further?

Sorry for the delay on update. They were able to get it resolving again.

I've been getting the same error too since the datacenter explosion... I've submitted 2 or 3 trouble tickets and still nothing... One time they didn't see anything wrong, and another time they supposedly fixed them...

I'll PM the guy above, hopefully he can resolve the issue because I'm getting a lot of bounces and even getting blacklisted (on ATT's Network) because of the lack of a proper PTR record!!!

Same problem here. Getting bounced from the ATT network due to lack of proper PTR record.

I'm having the same problem as well. It's been intermittent ever since the explosion. Support keeps telling me they either have fixed the problem or that it was already resolved, yet within hours the reverse lookups for my IPs do not resolve.

Support -- care to chime in here? This is obviously a major problem which needs to be resolved!

After 2 or 3 TT's... (which were quickly closed after the tech's thought they fixed it or nothing was wrong in the first place) and also PMing one of the tech support people here in the forum with the info the issue *still* isn't resolved...

I can dig the two NS servers and randomly one will still give a blank PTR record...

It's sad that they would dismiss this issue so quickly since having a PTR record is pretty vital to pass some anti-spam checks on email servers...

Usually I would be extremely ticked off and continue to persue the matter further, but I don't think it will ever get resolved unless it magically fixes itself... Nobody at TP seems to care (or maybe they just don't understand the problem).

I'm also excited my server from Dell should be arriving today, and hopefully by next week I can get it installed in its new colo facility... This was the last straw for me... If I can't send email reliably, my business suffers (as does any), so it's time to move on...

If you can PM me the ip you are experiencing issues with, we can look further into the issue. as a general rule of thumb, if your experiencing issues, if you 'update' your dns, it will push a re-sync to all of the servers. That is a good first step without having to rely on someone else if you can do it via servercommand.

I don't know if this has anything to do with this or not (Also having the ATT issues). But in my resolv.conf I have 70.84.160.11 and 70.84.161.11
The first of which has no rdns. Would this be causing an issue?

Edit: NM, I found updated resolvers for D5..