Reverse DNS Questions

Just moved site and RNDS seems screwy

[Duskrider]

I just recently moved my account from a shared hosting solution to a VPS (semi-managed) using Cpanel and WHM. I'm pretty new to the webserver thing, so even though I've used WHM, I haven't used all the advanced stuff on there.

Anyway, I was checking around on my new IP addresses that I got with my VPS to see if they were blacklisted anywhere, and it seems that doing a RDNS lookup on my main IP shows a nameserver I've never heard of. When I look up the domain it points to, the domain has expired. The other IP addresses on the account resolve to nothing at all.

Is there a way though WHM to fix this, or am I going to need to submit a ticket to my host? I'd rather do it on my own if I can, so at least I learn what's going on. I don't know enough to fool with DNS Zones and MX Entries without consulting greater minds first though. :)

[jtara]

You are going to have to submit a ticket to your host. You don't control the reverse DNS zone. Whoever "owns" the IP address does. It may be your host, it may be their colocation center, or some other upstream provider.

The reverse DNS doesn't have to point to your host name to be valid. In fact, many hosts won't do that for you. (Others will.) It has to point to a host name that resolves back to the same IP address.

Example:

www.example.com -> 1.2.3.4

4.3.2.1.in-addr.arpa -> vm100.examplehost.com

vm100.examplehost.com -> 1.2.3.4

It's valid.

In this case, vm100.examplehost.com is the canonical name for the IP address 1.2.3.4

[Duskrider]

I'll let my host know and see if they can do anything about it. That little example you put up there cleared the fog away much better than the four or five pages worth of technical jargon I looked through before I posted. Nice Job and much appreciated.