problems with Bluehost and custom domains on Tumblr

[zatelit]

Has anyone else experienced this problem?

I would like my tumblr account to point to use a custom domain name (i.e. www.mydomain.com goes to mydomain.tumblr.com)

(1) I reset my A-Record on Bluehost to 72.32.231.8
(2) I selected the "use custom domain" on my tumblr account to mydomain.com.

About 60% of the time if I enter mydomain.com I end up on my tumblr page (good); the other 40% of the time I end up on the Bluehost generic landing page (the one with the smug blond girl with the backpack scowling at you).

I assume this is a problem on Bluehost's end. Has anyone else experienced this and discovered a resolution? Should I try a different provider?

Thanks in advance -

[Ferdinand]

I have my tumblr blog (besides my Wordpress blog) running on a BH hosted subdomain and it works perfectly.

Did "Test your Domain" on Tumblr work?
If yes, you'll just have to wait a few hours.

If not, you did something wrong...

[zatelit]

I have my tumblr blog (besides my Wordpress blog) running on a BH hosted subdomain and it works perfectly.

Did "Test your Domain" on Tumblr work?
If yes, you'll just have to wait a few hours.

If not, you did something wrong...

I did the domain test on Tumblr and it worked.

It's been like this for a few weeks.

I know I didn't do "something" wrong.

[Ferdinand]

That's bad.
I have no idea if the a BH or a Tumblr problem...

[farcaster]

I would suggest that you contact Bluehost Support and have them examine your settings.

[zatelit]

I would suggest that you contact Bluehost Support and have them examine your settings.

Right.

Just in point of clarification of the other thread I started and you locked, my computer is most certainly virus free / trojan / spyware free and, further, I change my Bluehost password every 2 weeks to a randomized, 16-character string, so clearly that's not the issue.

I would be curious to know if others have experienced non-owned domains becoming parked on their Bluehost account and whether this was traced back to a registry/clerical error on Bluehost's part or other reasons? Unfortunately, if another user did experience this issue I guess I'll never know.