I've been having the ol' Hotmail dropping our mail issue and went t make everything was in order. Our reverse dns was still pointing to The Planet.

Since we outsource our DNS to easydns, I signed up for their reverse DNS service last night. They sent me the email asking me to ask the planet to change the delegation of our IPs.

As requested in their letter I opened a ticket and asked for the following changes to be made:

x.x.x.x.in-addr.arpa IN NS ns1.easydns.com.
x.x.x.x.in-addr.arpa IN NS ns2.easydns.com.
x.x.x.x.in-addr.arpa IN NS remote1.easydns.com.
x.x.x.x.in-addr.arpa IN NS remote2.easydns.com.

Support responded by saying "Apologies, but we do not delegate IP's to other parties for DNS administration purposes. I could edit the PTR for you, but we set PTR's at a ratio of 1 per IP address. If you would like us to edit the PTR for x.x.x.x, we would need a single entry to enter. We await your response."

Okay, so what's my next step? Do I just need The Planet to change my reverse DNS record and I don't need to use EasyDNS for the reverse stuff at all?

if all you use easydns for was reverse dns, then by all means cancel. We do not give out control over our ip ranges, unless the customer owns the entire range.

You just need to open a ticket, give us the ip, and what you want it to reverse resolve to, and we will set it up for you.

Thanks, I've opened the ticket.

What's the best way to handle the reverse DNS? Both mydomain.com and mail.mydomain.com point to the same IP. When I made the request in the ticket I asked for it to reverse to mail.mydomain.com as I read that some of the mail services (hotmail and aol) are looking for a three part domain and not just mydomain.com as part of their senderID/SPF issues.

mail.domain.com should be fine, if you have an SPF record, even better. Also if your mail is still bouncing to hotmail, you can open a ticket with abuse and let them know. They have some crazy hotmail voodoo magic that makes hotmail accept your mail.(until there is a complaint).

The reverse DNS change was made Saturday morning at around 2am according to the tech. How long should it take to propagate? (What's the TTL?) Doing an nslookup from the server is still showing theplanet.com 34 hrs. later.

Thanks.

nslookup is depreciated, use host... eg type "host 1.2.3.4" using the servers command prompt. The response should be mail.whatever.com.

it CAN take 24-72 hours, but if you are at the 34hr marker, you may want to consider waiting a few more hours, and opening another trouble ticket, request it be sent to IS-Unix, if you are using orbit, or development if you are using server command.

The reason I say this, is because if you put in the DNS ticket, chances are the change was made, but the zone file is not propagating correctly.