Remember this post (below) which explained how to make your Tumblr site a little more robust?
Well, it was fun while it lasted, but turns out that making this change may have broken your Tumblr today IFF your Tumblr site name does not end with “.tumblr.com” and IFF you followed those directions.
(If you never made the change below, or if you are not seeing the banner to update your settings, or if you do not have a custom domain name for your Tumblr, you can ignore this).
That’s (probably) why you’re seeing the banner telling you to update your site configuration.
Anyway, long story short, now is a good time to set those domains back to the recommended settings shown at: http://www.tumblr.com/docs/en/custom_domains.
Here’s a little geeky tidbit of Tumblr configuration that I wasn’t aware of (of use only if your Tumblr uses a custom domain, aka the URL doesn’t end in “.tumblr.com”):
One of Tumblr’s server went down today. It happens to be the one which is used to dish out webpages for those of us using a custom domain name (e.g. www.baohouse.net as opposed to baohouse.tumblr.com). Tumblr isn’t as fault-tolerant as I thought it was. However, there were other Tumblr servers that were still running fine.
So here’s a technique they don’t tell you that will make your Tumblr blog a little more robust. Remember when they said to add an A record with 188.8.131.52 as the value? Well, that’s just one server. What if that server goes down? Then you’re just out of luck. So let’s add multiple A records (yes, all of them!).
This image shows a typical A record scheme in GoDaddy. Your circumstance may be a little different. In this case @ = baohouse.net but you can put blog.baohouse.net in the host field if that is the address you want to use.
So if the first one goes down, your browser will move on to the second server, and if that goes down, to the third, and so on. For the techies out there, this is called a round-robin DNS technique.
I then use WhatsMyDNS.net to see if the record changes have been updated around the world. Usually it takes a few hours for the major/common servers to get the update.
Also, for those of you whose domain registrar only allows for a single A record, you may want to consider using another DNS provider. You can still keep the domain with your current registrar, just use a different name server.
I would appreciate it if you can reblog this and let your custom domain-using friends know.
Thanks for the the link to this post, thefrogman. I just reconfigured my A record, so I’m waiting for it to propagate.