Hello.

I have a STATIC IP 200.200.200.200 that is pointing to and verified by my ISP to domain.org. My domain.org is pointing to and verified to 200.200.200.200. I have absolutely no questions whatsoever that from the ISP and Domain Issuer (Dotster) that the Records are indeed correct, as they have been for 4 years and verified once again today.

When I go to a Reverse DNS test it fails; (imaginary IP and Domain)

Looking up Reverse DNS for IP Address: [200.200.200.200]

RDNS for 200.200.200.200 is: [domain.org.200.200.200.in-addr.arpa] - (PTR record - 200.200.200.200.in-addr.arpa)
ERROR - Lookup Failed for [domain.org.200.200.200.in-addr.arpa]
ERROR - Reverse Lookup Failed
IP [200.200.200.200] does not match []

When I do a DNS/ Forward lookup it comes back success.

Anyone have a direction I can look into because I have no idea how its happening when I visibly verify the correct records at the ISP where I lease the IP's as well as Dotster where I lease the Domain

You, or your ISP need to correct the PTR record for the IP 200.200.200.200.
Without more details, my guess is that you/ISP missed the trailing dot when you create the PTR record for domain.org, resulting in concatenating domain.org with 200.200.200.200.in-addr.arpa as you see in the snippet above.

Regards

Hello and thank you for your response. I understand what you are saying but still a little confused. Mostly on what do I ask them specifically... I talked to several people over the past 3 years and again last night via chat and they insisted the IP went to domain.org. They are obviously not going to listen to me unless I mention something greater than they are, like all tech support.
I miss the day I could go in to the account and manually set it all. If they insist again and I am stuck with no options am I able to create my own REVERSE or does it not work that way if they don’t cooperate in the procedure?

Hello and thank you for your response. I understand what you are saying but still a little confused. Mostly on what do I ask them specifically... I talked to several people over the past 3 years and again last night via chat and they insisted the IP went to domain.org. They are obviously not going to listen to me unless I mention something greater than they are, like all tech support.
I miss the day I could go in to the account and manually set it all. If they insist again and I am stuck with no options am I able to create my own REVERSE or does it not work that way if they don’t cooperate in the procedure?

Also is it because I had them point it to domain.org and not, let’s say, mail.domain.org or is that irrelevant. Mail shows up nowhere other than the hostname of the Linux email server box, no IP is associated with mail.x.x

As i told you, reading your OP, I can only think that there is an entry in the reverse zone file for the zone 200.200.200.200.in-addr.arpa that looks like this:
In the 1st line above since there is no trailing dot after the domain.org in the left side, the nameserver attaches in its response the zone name (200.200.200.200.in-addr.arpa) after the hostname, resulting in domain.org.200.200.200.in-addr.arpa.
Of course that's only a guess without knowing how your reverse zone file looks like.


This depends from your ISP, i.e. if they allow you to edit the PTR record(s) of the IPs you bought from them via some sort of a control panel.


If the MX record for your domain is just the plain "domain.org", you don't need to do anything else.

Well after several Internet Chats and finally getting someone ON-Shore who has experience with Reverse DNS we went over my account. He mentions he only has 3 Inputs; Hostname Domain IP. He mentioned the one and only getcord he can change had domain.org as Host, domain.org as Domain and x.x.x.x as the IP. He mentioned he has never really seen a Hostname simply be a x.org or like mail.x.org or so on so we decided "well it currently isn't working so" lets make the host mail.domain.org
Several hours later I am still getting the rDNS message. But I will say it now also mentions the mail.domain.org so it definitely went through. My Domain side at dotster has 10 "IP" sections and 2 "Domain" sections and changed both of them from domain.org to mail.domain.org (both were the MX @ and MX *). My linux email servers host is indeed mail and when I do all the correct tests they come back as correct domain and correct hostname and so on. My Postfix does indeed reflect mail.domain.org as well.

FCrDNS test result:
200.200.200.200 resolved to mail.domain.org.200.200.200.in-addr.arpa;
mail.domain.org.200.200.200.in-addr.arpa unresolved;
rDNS is NOT forward confirmed.

Generic PTR record test result:
mail.domain.org.200.200.200.in-addr.arpa looks like generic.

I have to assume that my ISP does not understand how to do it or that the 3 sections he is able to modify as I said simply are not inputting them correctly to whatever database they go into.

There was also an MX section but we did not mess with that... Is that also needed to be modified on ISP end for this to work or is this Reverse DNS issue something on its own?

Apparently changing domain.org to mail.domain.org has also changed the PTR record into mail.domain.org.200.200.200.in-addr.arpa. As I already told you, this happens when you omit the trailing dot in the FQDN
Tell support to add a trailing dot when they add/edit the PTR record, so it looks like this: mail.domain.org.

Just an update... I understand what you are saying about the trailing . At the end of mail.domain.org. or even domain.org. But the problem is that when a period added at the end of the “host” section (ALL we can modify is HOST and IP) it errors out as invalid. It will not accept a . At the end in the host section. It was a 2 hour call and we had various levels of tech support and each and every one said that the mail.domain.org and x.x.x.x were the way they always do them as they are the only 2 options they have.
Is there simply a chance that IANA has an issue with their side and it not inputting it correctly? Trust me I even copied and pasted what we spoke of to my phone notepad as to say exactly what should be done so on and so forth and they simply can not add a . At the end of the host portion.

This may sound dumb but could my ISP have their format so that I am given the ability to create my own Reverse DNS Record and that is why it comes back as generic and incorrect because there is no record?

Once again my guess is that they're talking about the forward zone (the A records in terms of dns), that according to what you've posted works ok.
Looking at dotster docs, I couldn't find any reference to PTR records. Maybe they don't support it, as they just host sites!
You should contact whoever you bought the 200.200.200.200 IP from, in order to clarify things.


This is not an IANA issue.
You must talk to whoever 200.200.200.in-addr.arpa zone belongs to. Running the following could give you more details:

Maybe. Usually when you buy a VPS, or a bunch of IPs, you're given a control panel, so you can manage them

I purchased a block of 8 Static IP’s, 5 usable, from CenturyLink, my ISP. They are the ones I speak of and that you mention are configuring the forward A (which I didn’t know they did forward anyway) (and I’ve always said my PTR and reverse dns to them)) and to that I still say they only have those 2 options. There are no other records such as PTR they can input. From my control panel through them I can have access to the same menu they do.
Maybe what I want is not an option available to me. Your are correct about the Dotster side that I understand. This is clearly the ISP side but what can I do when it’s the same answer and response and conversation with them? I am fine with the scenario if it’s something they don’t allow/support but I wanted to make sure it wasn’t me and with the endless help you’ve given me and me relating to them, it seems maybe it just isn’t going to happen.

D'oh, maybe this

Well I do not know if it’s a coincidence or because about 26 hours ago I wrote my own PTR Reverse DNS Record on my Email Server but for the first time in 3 years my Reverse DNS is working.
Is there a way to see where a PTR originated from? Such as it’s results versus what in my zone file to see if it was cause of me vs them?

You can use either one of the following commands to find the nameserver that is authoritative for an IP:

Meh, it must be what they did because the end results were

x.x.x.x.in-addr.arpa. 86400 IN PTR mail.domain.org.
x.x.x.in-addr.arpa. 86400 IN NS authns1.qwest.net.
x.x.x.in-addr.arpa. 86400 IN NS authns2.qwest.net.

And I never input that particular NS or IP it resolves to. I used the resolver.centurylink.net NS that was given. Ah well, it was fixed and definitely through your assistance and explaining it in crayon for me. I thank you and trust it I learned from this, wasn't just a waste.