3 ms·
Ok. My blog is up again. Thanks to cd34 and dangrossman to bring the DNS issue to my notice. When I first created my blog I was asked to point my domain's A-re
by anujkk 15y ago
Ok. My blog is up again. Thanks to cd34 and dangrossman to bring the DNS issue to my notice.
When I first created my blog I was asked to point my domain's A-record to their IP address but now the cached version of their help page(as I am unable to access any live page) is saying that if I am using subdomain, I need to point the CNAME record to domains.tumblr.com. I did that and my blog is up again.
Still I am unable to access any page of tumblr.com other than signup page. :)
- cd34 15y agoAre you behind a proxy server? In Chrome, do you have the Developer toolbar, if so, Toolbar, Information, View Response Headers, what is the Content-type? Firefox has similar tools, HeaderSpy will also do it. If the content type is wrong as you suggested in an earlier post, it would indicate a problem between you and tumblr.com. If the response is valid, it would suggest a problem, perhaps with an extension (though, if it happens across multiple browsers, that is unlikely). curl -I https://www.tumblr.com/ https://www.tumblr.com/ (or some url that has just given you problems) - Is the content type correct on that? Do you have anything in your hosts file that might be overriding their IPs? Disable gzip compression in your browser, try again. I know that some versions of Firefox and Chrome had issues with gzip - preferring deflate and tumblr appears to be sending gzip. Though, those issues were fixed in recent (last few months) versions of both. Also, what IP address or addresses does your machine believe belong to www.tumblr.com?