Chat Online
Support

Forum

A place for Dynadot and community experts alike to ask questions, share ideas, and more.
Tumblr: Domain Forwarding Disaster
7/9/2012 15:29
Hello, I would like to get some help on my massive forwarding issues. I don't know whose error is that, Dynadot's or Tumblr's, but either way, it seems pretty complex:

I bought a domain for my Tumblr blog. First, when I managed to make forwarding work, it redirected to my blog and either didn't display my domain at all or (with stealth forwarding) displayed my domain on EVERY page. That didn't work. I tried to follow some DNS instructions for Tumblr, and it only made things worse.

First of all, the instructions on Dynadot for setting up domain for Tumblr differ from instructions on Tumblr (http://www.tumblr.com/docs/en/custom_domains), but either ones don't seem to work. While Dynadot says I should point to 72.32.231.8 in my DNS settings, Tumblr says it should be 66.6.44.4; Dynadot says I need to point only to the A-record, and Tumblr says that for a three level domain (i.e. www.domain.com) I should point CNAME record to domains.tumblr.com.

Either way, now  my domain points to a Not Found page on Tumblr, and when I check tumblr settings to test the domain, it says that my A-record should point to 66.6.44.4 (which it does), and when I check www.domain.com, it says that the CNAME should point to domains.tumblr.com (which it also does).

So, why does Tumblr say that my A-record and CNAME are wrong, even if the changes have already been made? My domain still displays an error page.

Any help? Thanks.
Reply Quote
7/11/2012 14:47
Yes,  there is always some wait time involved when you make these kinds of changes.  Glad to hear everything is working properly now.
Reply Quote
7/11/2012 13:29
Hello again!

Yes, I updated my custom domain info in Tumblr settings, but it reported an error message for a while, even though I did everything right. Now it finally cleared up. One by one the errors went away (not all at once) and now my domain points to Tumblr.

Thanks anyway!
Reply Quote
7/10/2012 15:35
I'd suggest you use whatever settings they currently tell you to use.  I'm not sure when our Help section topic was written, but it's possible and likely, that they have made some changes, including the IP which should be used.  

So, why does Tumblr say that my A-record and CNAME are wrong, even if the changes have already been made? My domain still displays an error page.

I looked at your settings and compared them to their current help topic on the matter, and everything you've set up here looks perfect.

Have you already set the custom domain name in your Tumblr account?  That would be my guess as to why you are seeing that "page not found" error.
Reply Quote
7/10/2012 14:39
Tech Support, anyone?
Reply Quote