Webmasters Stack Exchange is a question and answer site for pro webmasters. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A site I administer recently rebranded under a new domain name. I updated the DNS to forward the old to the new, but reverse IP lookups are still resolving to the old domain. I don't see anywhere in my DNS settings where this could be a problem. Will this take longer than a regular DNS update or is there something else I can do to fix this?


share|improve this question

The reverse DNS isn't usually set on your server but by the host datacentre that manages your server. When I setup a new server I usually send a message to the support saying, "Please set reverse DNS for host.example.com to and please remove reverse DNS for old.example.com."

share|improve this answer
Thanks! For those of you who got here with the same problem and you are hosting with Rackspace, the reverse IP lookup is on the 'DNS' tab (duh!) of your server...I never thought to check here as I thought the problem was with a DNS server. – Tristen Jun 30 '11 at 4:06
Shouldn't it be the other way round: "Please set reverse DNS for to host.example.com ..."? – DocRoot Apr 21 at 14:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.